System and method for using intelligent codes in conjunction with stored-value cards

ABSTRACT

A system and method of transacting a prepaid product with an electronic mobile device that is used to electronically interface with a code, such as a QR code, bar code, RF signal or NFC signal, representing a prepaid product. The codes of multiple prepaid products of multiple prepaid product providers are grouped together on a single structure or in a single computer displayed in a shopping area. The electronic mobile device subsequently electronically interfaces with a point of sale device after electronically interfacing with said code to provide prepaid product information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 17/481,420, filed on Sep. 22, 2021, and entitled“System and Method for Using Intelligent Codes in Conjunction withStored-Value Cards,” which is a continuation of and claims priority toU.S. patent application Ser. No. 17/220,683, filed on Apr. 1, 2021, andentitled “System and Method for Using Intelligent Codes in Conjunctionwith Stored-Value Cards,” which is a continuation of and claims priorityto U.S. patent application Ser. No. 14/085,394, filed on Nov. 20, 2013,and entitled “System and Method for Using Intelligent Codes inConjunction with Stored-Value Cards,” which claims priority to U.S.Provisional Patent Application Ser. Nos. 61/728,597 filed on Nov. 20,2012, and entitled “Endless Endcap;” and 61/800,704 filed on Mar. 15,2013, and entitled “System and Method for Using QR Codes in Conjunctionwith Electronic Stored-Value Cards,” which applications are incorporatedby reference herein in their entirety.

This application also incorporates by reference the entirety of thedisclosure, the subject matter, and concepts of: InternationalApplication Serial No. PCT/US13/26501, filed on Feb. 15, 2013, andentitled “System and Method of Registering Stored-Value Cards IntoElectronic Wallets”; U.S. patent application Ser. No. 12/538,083, filedAug. 7, 2009, and entitled “Transaction Processing Platform forFacilitating Electronic Distribution of Plural Prepaid Services” whichis a continuation of U.S. patent application Ser. No. 12/338,854, filedDec. 18, 2008, which is a continuation of U.S. patent application Ser.No. 11/851,337, filed Sep. 6, 2007 (now U.S. Pat. No. 7,477,731), whichis a continuation of U.S. patent application Ser. No. 11/007,662, filedDec. 7, 2004 (now U.S. Pat. No. 7,280,644); U.S. patent application Ser.No. 13/040,074 filed Mar. 3, 2011 and entitled “System and Method forElectronic Prepaid Account Replenishment;” U.S. patent application Ser.No. 10/821,815, filed Apr. 9, 2004 and entitled “System and Method forDistributing Person Identification Numbers Over a Computer Network;”U.S. patent application Ser. No. 12/786,403, filed May 24, 2010, andentitled “System and Method for Distributing Person IdentificationNumbers Over a Computer Network;” U.S. patent application Ser. No.12/711,211, filed Feb. 23, 2010, and entitled “System and Method forDistributing Person Identification Numbers Over a Computer Network;” andU.S. patent application Ser. No. 12/719,741, filed Mar. 8, 2010, andentitled “Systems and Methods for Personal Identification NumberDistribution and Delivery.”

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

FIELD OF THE INVENTION

The disclosure generally relates to the use of electronic stored-valuecards in electronic transactions.

BACKGROUND

The electronic transaction market is currently filled with many types ofcredit cards, debit cards, stored value cards, and loyalty cards, all ofwhich may be offered by different issuers, vendors, and providers. Someof the cards are tailored to be redeemed from a retailer while othersmay be redeemed by financial institutions. Other cards have promotionsattached to them, e.g., loyalty cards. However, the increasing quantityand complexity of the cards makes organization and redemptionincreasingly difficult, thus potentially hindering the growth of themarket. For example, a user may not know or remember that the user has astored value card for a specific store during a purchase at that storebecause the user has too many stored value cards. Also, a user may notunderstand the various types of promotions available to him using a cardin combination with a loyalty card, and as such, may not benefit frompromotions applicable to the user's purchase. Historically, cards havebeen embodied in a tangible medium such as plastic, and thus aresusceptible to loss, theft, or simply being left at home when needed.With the continued growth in card-based transactional offerings providedto consumers, many consumers are faced with the burdensome task oforganizing, managing, tracking, transporting, and storing all of theircredit, debit, stored-value, loyalty, and other types of merchant,vendor, and provider issued cards. What today's consumers need is a moreefficient, secure, and effective way of accessing and using theircard-related assets.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart depicting an embodiment of a method for providingan electronic stored-value card via a QR code scan.

FIG. 2 is a flowchart depicting another embodiment of a method forproviding an electronic stored-value card via a QR code scan.

FIG. 3A is a schematic illustration of an embodiment of a system forproviding an electronic stored-value card via a QR code scan.

FIG. 3B is a schematic illustration of another embodiment of a systemfor providing an electronic stored-value card via a QR code scan.

FIGS. 4A, 5A, 5B, and 5C are schematic representations of an electronicvalue token transaction processing system in accordance with at leastone embodiment.

FIG. 4B illustrates an exemplary embodiment of an electronic wallet.

FIGS. 6A, 6B, and 6C are front perspective views of representativeindividual proxy cards in accordance with at least one embodiment.

FIG. 6D is a front perspective view of a representative user device inaccordance with at least one embodiment.

FIG. 7A is a flowchart depicting exemplary processes utilized by anelectronic value token transaction computer for creating an electronicwallet or adding/redeeming value tokens to/from the electronic wallet inaccordance with at least one embodiment.

FIG. 7B is a flowchart depicting exemplary processes utilized by anelectronic value token transaction computer for creating an electronicsub-wallet or adding/redeeming value tokens to/from the electronicsub-wallet in accordance with at least one embodiment.

FIG. 8 illustrates a particular machine suitable for implementing theseveral embodiments of the disclosure.

FIGS. 9A-D illustrates a series of user interface screens and prompts inaccordance with at least one embodiment.

DETAILED DESCRIPTION

Disclosed herein are systems and methods for using stored-value cards,such as physical stored-value cards and electronic stored-value cards(hereinafter “eSVC” or “eSVCs”). Particularly, the systems and methodsdisclosed herein may provide an eSVC in response to a user request(hereinafter “eSVC Request”). In an embodiment, the eSVC Requestcomprises an eSVC identifier (hereinafter “intelligent code”). In anembodiment, the intelligent code comprises a barcode; a QR code; anarrangement of numerals, letters, symbols, images, and/or colors; anelectromagnetic signal (e.g., near field communication (“NFC”),infrared, RFID); a mechanical wave (e.g., sound); or combinationsthereof. In an embodiment, the intelligent code is may be interpreted,scanned, input, and/or read (“scan” may be used to reference any of theforegoing) by a user's device via voice recognition, cameramanipulation, physical gesture (e.g., finger swipe), NFC communication,Bluetooth communication, or other known methods for engaging a user'sdevice for information reception. The intelligent code may be conveyed,transmitted, delivered, or otherwise communicated to an eSVC providerand/or distribution system via phone line, cellular communication, Wi-Ficommunication, Bluetooth communication, radio communication, USB,MiniPin, email, webpage interaction, internet communication, VoIP, shortmessage service (“SMS”), Instant messaging, infrared communication,Android Beam, or other methods of communication known to those of skillin the art. Additionally, the disclosed systems and methods may provideelectronic stored-value card users a guided process for registeringelectronic stored-value cards into existing and new electronic wallets,and the use of value tokens in the electronic wallet(s) for electronictransactions.

Acquisition and/or purchase of a stored-value card (e.g., a physicalstored-value card or an electronic stored-value card) may involve anaccount vendor, a redeeming merchant, and an account issuer. In variousembodiments, the account vendor, redeeming merchant and account issuermay be the same, different, or related entities. The point of sale wherethe stored-value card is purchased and/or acquired is referred to hereinas the account vendor or simply vendor. An entity that will accept valuecontained in the stored-value card for business transactions, forexample, as tender for a purchase, is referred to as a redeemingmerchant. An entity that provides the financial backing and/or paymentprocessing accessed via use of the stored-value card is referred to asthe account issuer, or simply, issuer. Account issuers may includedirect issuers of stored-value cards such as store-branded cards (e.g.,Macy's, Target), and in some embodiments the account vendor may also bethe account issuer and/or the redeeming merchant. Account issuers alsomay include banks, financial institutions, and processors such as VISA,Mastercard, American Express, etc., and stored-value cards issued bysuch institutions may be readily accepted by a number of redeemingmerchants to conduct transactions such as purchases. Account issuers maybe in various industries, such as the entertainment, health, medical,pharmaceutical industries. For example, the account issuer may be apharmaceutical company utilizing promotional physical and/or electronicstored-value cards for pharmaceutical products. In some instances, astored-value card may be sold and/or issued at the same or differentaccount vendor (e.g., account vendor is Store X or a different orunrelated Store Z). In such instances, the Store X branded stored-valuecard may be issued by Store X, by Store Z, or by a third party such asbank or financial institution.

Card product retailers often carry displays having manypackaged-physical card products from a variety of brands. Such displaysmay be referred to as “endcaps.” As such, a consumer or customer of theretailer may purchase a variety of physical card products. A consumer orcustomer may need to purchase multiple card products at in a singletransaction, giving rise to a problem of managing the multiple cardproducts. Additionally, when a retailer sells packaged-physical cardproducts, e.g., via an endcap, the supply of products is subject togoing “out of stock,” giving rise to lost sales. Moreover, manufacturingand distribution costs are associated with packaged-physical cardproducts. The disclosed methods and systems allow for a customer orconsumer to purchase card products without the hassle of managingphysical cards and/or packages. Additionally, the disclosed methods andsystems allow for the sale of electronic stored-value cards in place ofphysical cards, eliminating costs associated with the manufacture anddistribution of physical card products.

As used herein, “electronic-stored value card” or “eSVC” refers to anelectronic embodiment of an account that may be used to transactbusiness with a merchant willing to accept a value (e.g., points, miles,dollars, or any other measure of value such as a value token describedhereinbelow), for example as tender for a purchase or discount for apurchase. As used herein, “electronic stored-value card” or “eSVC” mayadditionally or alternatively refer to an electronic embodiment of anaccount used for promotional and/or marketing purposes. The accounts maycomprise credit accounts, debit accounts, gift accounts, telephoneaccounts, loyalty accounts, membership accounts, ticket accounts,entertainment accounts, sports accounts, prepaid accounts, discountaccounts, healthcare accounts, the like, or combinations thereof. Suchaccounts may be associated with corresponding physical cards, includingcredit cards, debit cards, gift cards, telephone cards, loyalty cards,membership cards, ticket cards, entertainment cards, sports cards,prepaid cards, discount cards, healthcare cards, the like, orcombinations thereof. Such accounts may additionally or alternativelycomprise electronic accounts, such as electronic credit accounts,electronic debit accounts, electronic gift accounts, electronictelephone accounts, electronic loyalty accounts, electronic membershipaccounts, electronic ticket accounts, electronic entertainment accounts,electronic sports accounts, electronic prepaid accounts, electronicdiscount accounts, electronic healthcare accounts, the like, orcombinations thereof. In embodiments, the value of an electronicstored-value card may be embodied as an “electronic value token” or“value token,” both of which are described in detail hereinbelow.

In embodiments, before the user obtains (e.g., receives, activates,redeems, or combinations thereof) the eSVC, the eSVC provider, thee-wallet provider, the eSVC processor, the eSVC issuer, the merchant, orcombinations thereof may provide fraud mitigation. In an embodiment,providing fraud mitigation may comprise blocking access to an eSVCbefore a user views the eSVC, blocking access to an eSVC before a useractivates the eSVC, or both. In an additional or alternative embodiment,providing fraud mitigation may comprise determining a digitalfingerprint of a user device (e.g., user device 14), at the time a userattempts to view an eSVC to determine the risk associated with the user,the eSVC, or both. In an additional or alternative embodiment, providingfraud mitigation may comprise withholding the providing of the eSVC(e.g., withholding the delivery of redemption information for the eSVC).In an additional or alternative embodiment, providing fraud mitigationmay comprise determining a geographic location of the eSVC and/or userand pausing the providing of the eSVC for a period of time determined bythe geographic location. For example, the providing of the eSVC may beheld for a longer period of time in geographic locations known ordetermined to be of high risk of fraud, and the providing of the eSVCmay be held for a short period of time or for a period of timecomprising zero in geographic locations known or determined to be of lowor no risk of fraud.

FIGS. 1 and 2 shows flowcharts of embodiments of methods for providingan eSVC via receipt of an intelligent code. The various steps of themethods may be omitted, substituted, and rearranged except wherespecified hereinbelow. In an embodiment, the intelligent code may conveya request for multiple eSVCs, e.g., an eSVC for a restaurant and eSVCfor a movie theater. For example, a user Request may include anintelligent code that was scanned by a user which was offered as a“Dinner and a Movie” intelligent code (hereinafter a “combo code”),wherein the entity offering the intelligent code only offers thecombination and does not offer the corresponding restaurant eSVC andmovie theater eSVC as separately available items for purchase but theuser receives the result of the requested combo code as two separateeSVCs. Moreover, the two separate eSVCs may be delivered to differentrecipients upon request. Moreover, the eSVCs may also be subject to thefraud mitigation capabilities described above.

The method in FIG. 1 starts at block 20. At block 20, a intelligent codeis received. The intelligent code is associated with a request for aneSVC, a request for a tutorial for obtaining the electronic stored-valuecard via an intelligent code, or both. That is, a request for an eSVCmay be conveyed via a transmission of an intelligent code, a tutorialfor obtaining the eSVC may conveyed via a transmission of an intelligentcode, or both may be conveyed by the transmission of one or moreintelligent codes. In an embodiment, the eSVC Request may compriseadditional user provided information (e.g., zip code of location) oradditional user device provided information (e.g., geographic locationinformation based on GPS or other locationing methods). Theabove-described additional information may be used by an eSVC processor,an eSVC issuer, or an eSVC processor/issuer to filter eSVC offeringsavailable for the identified geographic location. In embodiments, theintelligent code may include information comprising eSVC activationinformation, eSVC redemption information, eSVC reload information,retailer identification (e.g., store ID), eSVC brand, rack, eSVCcategory, GPS coordinates of the user (e.g., of the merchant locationand/or user's mobile device), type of user device (e.g., of the user'smobile device), identification of the user device, IP address, one ormore email addresses, a requested value for the eSVC, whether therequest is for multiple eSVCs (e.g., a combo code), e-wallet accountinformation (e.g., e-wallet login), loyalty program information (e.g.,loyalty number, loyalty login information), where to deliver the eSVC(e.g., a third-party via communication means described herein), whetherthe user wishes to purchase now or later, whether the user wishes topurchase in-store or online, other information known to those skilled inthe art with the aid of this disclosure, or combinations thereof. In anembodiment, the intelligent code does not comprise information which canbe used to redeem, activate, reload, or use an electronic stored-valuecard. A tutorial may comprise a ‘Try Me’ app where a user can scan anintelligent code and follow the various method steps without actuallypurchasing an eSVC. The tutorial may alternatively comprise a websiteexplaining how the intelligent code method works for obtaining an eSVC.The tutorial may alternatively comprise a demo video of how to conveythe intelligent code to obtain an eSVC. The tutorial may additionallycomprise a link to move the user to a live purchase of an eSVC accordingto the embodiments disclosed herein.

A customer or consumer of card products (also referred to herein as a“user” in the disclosed embodiments) may generally make the request forthe eSVC at a physical retail (e.g., merchant) location, an onlinemerchant portal, via a user device (e.g., user device 14 of FIGS. 3A and3B), or combinations thereof. A physical retail location or onlinemerchant portal may have a physical or virtual “endcap” which is adisplay for the intelligent codes for various brands and/or values ofeSVCs or combinations of eSVCs. Thus, no physical card products areneeded because purchase of the eSVC is initiated with a scan of anintelligent code of a desired eSVC. However, the virtual “endcap” may beemployed for the sale and or delivery of physical stored-value cards aswell, such as to promote the sale of physical “multipacks,” e.g., apackage which contains multiple cards to be purchased an activated,wherein the multiple cards may share a common issuer or may not share acommon issuer. Because the endcap (virtual or physical display) uses nophysical cards in order to sell eSVCs, no distribution or manufacture ofphysical card products is needed. However, embodiments disclosed hereincontemplate an intelligent code may be located on the front or back of aphysical stored-value card. The physical stored-value card may comprisea known form of stored-value cards often referred to as a credit card, adebit card, a gift-card, a loyalty card, a rewards card, a membershipcard, a discount card, a promotional card, etc. Thus, embodimentsdisclosed herein may be used with physical stored-value cards, which maybe converted to eSVCs by first scanning the intelligent code of thephysical stored-value card to request an eSVC.

The request for an electronic stored-value card may comprise a requestto view a selection of eSVCs available for purchase, a request to viewan eSVC value available for purchase, a request to purchase an eSVC (ormultiple eSVCs), or combinations thereof. In response to a request toview a selection of eSVCs, an entity (e.g., an eSVC processor, an eSVCissuer, or an eSVC processor/issuer) may provide the selection of eSVCsavailable for purchase and/or exchange (e.g., in an eSVC exchangeservice) to the user, the selection of eSVC values available to theuser, eSVC purchase information as described hereinbelow, orcombinations thereof.

At block 21 of FIG. 1 , an eSVC shopping cart is established. The eSVCshopping cart may be established in response to the received intelligentcode scan. The eSVC shopping cart may comprise a digital representationof a physical shopping cart used to buy goods or services (e.g., such asthe shopping carts commonly used on merchant websites to purchase goodsor services (e.g., a hotel website, an airline website, a bookstorewebsite, etc.). The eSVC shopping cart may comprise unactivated eSVCsassociated with the received intelligent code scan. For example, afteran eSVC processor receives a QR code scan from a user, the eSVCprocessor may create an eSVC shopping cart which stores the QR codeinformation identifying the eSVC associated with the QR code. The eSVCshopping cart may also associate any information captured in block 22 ofthe method of FIG. 1 with one or more eSVCs therein. The eSVC in theeSVC shopping cart may comprise an unactivated state. For example, as adigital representation of the eSVC status on a device such as the user'smobile device, the eSVC shopping cart may be shown as a webpage, popupwindow, app, or combinations thereof, and the eSVC may be shown with avisual identifier such as a logo or icon (e.g., a Brand X logo if theeSVC is a Brand X eSVC). The visual identifier may be made transparentand/or without interactivity on the user's device to indicate the eSVCis in the eSVC shopping cart but not yet activated. In embodiments, theeSVC shopping cart is not displayed to the user until the user purchasesand activates the eSVC.

At block 22 of FIG. 1 , information may be captured in response to therequest for an eSVC. In addition to information contained in theintelligent code, captured information may comprise GPS coordinates ofthe user (e.g., of the user's mobile device), type of user device (e.g.,of the user's mobile device), identification of the user device, IPaddress, one or more email addresses, a requested value for the eSVC,whether the request is for multiple eSVCs, e-wallet account information(e.g., e-wallet login), loyalty program information (e.g., loyaltynumber, loyalty login information), where to deliver the eSVC (e.g., athird-party via communication means described herein), whether the userwishes to purchase now or later, whether the user wishes to purchasein-store or online, other information known to those skilled in the artwith the aid of this disclosure, or combinations thereof. Inembodiments, the user may be prompted on a device (e.g., a user device)and asked to submit the information which is desirably captured. Theuser may enter and submit the information, may deny entering theinformation, may request to enter the information later, may take noaction, or combinations thereof. In embodiments wherein the eSVCshopping cart has not been paused before capturing information andpausing the eSVC shopping cart is desired, flow may proceed from block22 to block 23 of FIG. 1 . In embodiments where the eSVC shopping carthas already been paused or pausing is not desired, flow from block 22 ofFIG. 1 may proceed to block 24 of FIG. 1 ; alternatively, to block 25 ofFIG. 1 ; alternatively, to block 26 of FIG. 1 .

At block 23 of FIG. 1 , the eSVC shopping cart may be paused. Forexample, the provider of the eSVC shopping cart, e.g., the eSVCprocessor or the eSVC issuer, may pause further activity associated withthe eSVC shopping cart (in embodiments, other than adding more eSVCs viaintelligent code scan). In embodiments, activity associated with theeSVC shopping cart may be paused until a condition is satisfied, such asa purchase of an eSVC, an activation of an eSVC, or in one-stepactivation scenarios, the purchase and activation of the eSVC. Inembodiments where information is not captured before pausing the eSVCshopping cart and captured information is desired, flow proceeds toblock 22 of FIG. 1 . In embodiments where information has already beencaptured or is not desired, flow may proceed to block 24 of FIG. 1 ;alternatively, to block 25 of FIG. 1 ; alternatively, to block 26 ofFIG. 1 .

In the disclosed embodiments, the user may choose (e.g., via a promptembodied as a selection screen, popup window, which can be promptedwhile entering information at block 22 of FIG. 1 , etc.) to purchase theeSVC via in-store purchase (e.g., via a point-of-sale device) or via anonline payment portal (e.g., provided by a computer device of the eSVCprocessor which acts as an online merchant for the purchase of the eSVC,of a third-party merchant, or of an eSVC issuer which acts as an onlinemerchant for the purchase of the eSVC). In embodiments, the user mayautomatically be taken to online payment unless the user elects not topurchase online, or the eSVC may automatically be prepared (e.g.,according to blocks 24 and 25) for in-store purchase unless the userelects not to purchase in-store. In embodiments, the user may use a userdevice to request the online purchase without need for a point-of-saledevice, e.g., via an online payment portal, or the user may use the userdevice to elect in-store payment for the eSVC. If the user requestsonline payment, flow may proceed to block 26. If the user elects to payin-store, flow may proceed to block 24 or block 25 depending on whichentity (e.g., eSVC processor or eSVC issuer) provides the barcode andactivation information for the eSVC. In embodiments, the user may choosenot to purchase at the time of prompting, and the eSVC shopping cart mayremain paused as discussed in block 23 until further action is taken(e.g., in-store purchase of the eSVC, online purchase of the eSVC,deletion of the eSVC from the eSVC shopping cart, etc.).

At block 24 of FIG. 1 , purchase information (e.g., a barcode and/oractivation information) for the eSVC purchase is obtained. Inembodiments, purchase information is obtained after the user chooses topurchase the eSVC in-store. In an embodiment, the entity processing thepurchase of the eSVC (i.e., via the initiating intelligent code scan)may not be the same entity as the issuer of the eSVC. The processingentity may obtain the barcode and/or activation information of therequested eSVC from another entity such as the issuer of the eSVC. Theissuer of the eSVC may generate, or retrieve a pre-generated, uniquebarcode and/or activation information for purchase of the eSVC. Thebarcode may comprise an EAN128 barcode, a dynamic EAN128 barcode, or aUPC. Activation information may comprise an activation code. In anembodiment, the barcode comprises the activation information in anissuer account portion of the barcode. Additionally the barcodecomprises a vendor product identification in a vendor productidentification portion of the barcode.

At block 25 of FIG. 1 , purchase information (e.g., a unique barcodeand/or unique activation information) for the eSVC purchase is provided(e.g., made available for retrieval, sent via digital communication,etc.). In an embodiment where the entity processing the purchase of theeSVC (i.e., via the initiating intelligent code scan) may be the issuerof the eSVC, the processing entity may generate, or retrieve apre-generated, unique barcode and/or activation information for purchaseof the eSVC. The eSVC processor may then provide (e.g., send) thebarcode and/or activation information to the user (e.g., via userdevice), to a merchant (e.g., via a merchant computer device, describedin the discussion for FIG. 3B), or combinations thereof. In anembodiment where the processor of purchase of the eSVC is an entityseparate from the issuer of the eSVC and the issuer is responsible forproviding barcode and/or activation information, the issuer of the eSVCmay provide (e.g., send) the barcode and/or activation information tothe processor of the eSVC (e.g. for forwarding to the user), directly tothe user (e.g., via a user device), to the merchant (e.g., via amerchant computer device, described in the discussion for FIG. 3B), orcombinations thereof. After performing the step at block 25 of FIG. 1 ,flow may proceed to block 28 of FIG. 1 .

At block 26 of FIG. 1 , an online payment portal may be provided. Inembodiments, an online payment portal may be provided (e.g., by the eSVCprocessor acting as a merchant, or by a third-party merchant) to theuser through which the user may purchase the eSVC. The online paymentportal may request payment information (e.g., account number, expirationdate, security code) for a card other than the eSVC being purchased(e.g., a physical card, another eSVC, or combination thereof). The user,e.g., via the user device, may enter the payment information (e.g., cardnumber (or another eSVC number), billing address (postal code),expiration date, security code, or combinations thereof) and the paymentinformation may be processed by the eSVC processor (in embodiments wherethe eSVC processor provides the payment portal), or by a third-partymerchant that forwards the payment information to the eSVC processor.

At block 27 of FIG. 1 , purchase verification is received. The purchaseverification may comprise an activation request of the eSVC. Inembodiments where the eSVC is purchased in-store, the barcode may besent to and displayed on a user device (e.g., the user's mobile device),and the user may scan the barcode displayed on the user device (or havethe barcode scanned by in-store personnel) with a merchant computerdevice (e.g., a point-of-sale terminal of a merchant). Scanning thebarcode and activation information may be considered a one-stepactivation method, as opposed to a two-step activation method where thebarcode and activation information are separately provided and purchaseof the eSVC is a separate step from activation of the eSVC. The one-stepactivation of the eSVC embodied by scanning the barcode and activationinformation may comprise simultaneously or serially (e.g., one afteranother without separate request) scanning the barcode and activationinformation (e.g., comprising an activation code, a vendor productidentification, an issuer account code, or combinations thereof) at amerchant computer device (e.g., point-of-sale terminal). One-stepactivation of the eSVC only requires a single entry by a clerk operatingthe point-of-sale terminal to activate the eSVC. For example, the onestep may be performed at the point-of-sale terminal by scanning thebarcode, (e.g., an EAN/UCC-128 barcode) comprising both a vendor productidentification portion and an issuer account portion. The vendor productidentification portion may be used to perform a look-up to determineeSVC identity and price, or may contain the eSVC identity and pricewithout need for merchant look-up. In embodiments, the price does notmatch the value of the eSVC, for example, when a promotional offer sellsan eSVC of a greater value (e.g., $30) for a price of a lesser value(e.g., $20). The issuer account portion may be used to activate theparticular account associated with the eSVC such that the eSVC may beused (e.g., to transact business with a merchant). Upon being entered atthe point-of-sale terminal, the issuer account portion may be conveyed(for example, via a network described hereinbelow) to, and received by,the issuer of the eSVC (e.g., as a purchase verification and/or anactivation request); the issuer account portion may be conveyed (forexample, via a network described hereinbelow) to, and received by, theprocessor of the eSVC (e.g., as a purchase verification and/or as anactivation request); the issuer account portion may be conveyed (forexample, via a network described hereinbelow) to, and received by, athird-party eSVC processor responsible for activating the eSVC (e.g., asa purchase verification and/or as an activation request); orcombinations thereof. Once the purchase verification and/or activationrequest is received, the processor, issuer, third-party processor, orcombinations thereof, may activate the eSVC via methods known in the artwith the aid of this disclosure.

In embodiments with an online purchase of the eSVC, the barcode may notbe provided. In online purchase embodiments, when the online paymentportal requests payment information (e.g., account number, expirationdate, security code) for a card other than the eSVC being purchased(e.g., a physical card, another eSVC, or combination thereof), the user,e.g., via the user device, may enter the payment information (e.g., cardnumber (or another eSVC number), billing address (postal code),expiration date, security code, or combinations thereof) and the paymentinformation may be processed by the eSVC processor (in embodiments wherethe eSVC processor provides the payment portal), or by a third-partymerchant that forwards the payment information to the eSVC processor.Upon online payment, a purchase verification may be conveyed (forexample, via a network described hereinbelow) to, and received by, theissuer of the eSVC (e.g., as a purchase verification and/or anactivation request); the purchase verification may be conveyed (forexample, via a network described hereinbelow) to, and received by, theprocessor of the eSVC (e.g., as a purchase verification and/or as anactivation request); the purchase verification may be conveyed (forexample, via a network described hereinbelow) to, and received by, athird-party eSVC processor responsible for activating the eSVC (e.g., asa purchase verification and/or as an activation request); orcombinations thereof.

Once the purchase verification and/or activation request is received,the processor, issuer, third-party processor, or combinations thereof,may activate the eSVC via methods known in the art with the aid of thisdisclosure. In embodiments, the purchase of the eSVC may be processed bythe provider of the eSVC and/or e-wallet (e.g., via eSVC processor), bya merchant, by the eSVC issuer, or combinations thereof. In anembodiment, the purchase may be processed by applying a purchase valueto complete the transaction. In an embodiment, to process the purchase,authentication information to process the purchase may be identified, avalue associated with the eSVC (e.g., embodied as a value token,described below) may be assigned, at least a portion of the value ofanother eSVC (e.g., value token) may be applied to at least a portion ofthe purchase price, at least a portion of the value of a physical cardmay be applied to at least a portion of the purchase price, orcombinations thereof. In an embodiment, identifying authenticationinformation may comprise authentication techniques known to thoseskilled in the art with the aid of this disclosure. In embodiments,processing the purchase may further comprise processing at least aportion of the purchase in a primary wallet of an e-wallet (e.g.,electronic wallet 10 of FIG. 3A), processing at least a portion of thepurchase in a sub-wallet of an e-wallet (e.g., of electronic wallet 10of FIG. 3A), or both. In embodiment, a notification may be sent to theuser, merchant, processor, and or issuer that the purchase has beenprocessed. After performing an embodiment of the step at block 27 ofFIG. 1 , flow may proceed to block 28 of FIG. 1 .

At block 28 of FIG. 1 , the eSVC shopping cart is unpaused. Inembodiments, the eSVC shopping cart is unpause after purchase of an eSVCcontained therein, after activation of an eSVC therein, or both. Inembodiments, the eSVC shopping cart is unpaused only for the eSVCpurchased and/or activated while the eSVC shopping cart remains pausedfor non-purchased and/or unactivated eSVCs. Flow may proceed to block 29of FIG. 1 ; alternatively, to block 30 of FIG. 1 ; alternatively toblock 31 of FIG. 1 .

At block 29 of FIG. 1 , the purchased and activated eSVC may be added toan electronic wallet (e.g., of the user). As used herein, an “electronicwallet” (also referred to as “e-wallet”) may include an electronicallymaintained data file (e.g., maintained on a computer device of aprovider of the electronic wallet, for example, the eSVC processor)which may comprise pre-existing eSVCs, authentication information, rulesfor use, sub-wallets (e.g., for separately maintaining eSVC-relatedinformation), and electronic value tokens (e.g., electronicrepresentations of the monetary and/or other value associated with theelectronic stored-value card-related information contained in thee-wallet/sub-wallet). The eSVC processor may prompt the user (e.g.,before or after activation of the eSVC) whether the user would like tocreate an electronic wallet and add the eSVC thereto, or whether theuser has a pre-existing e-wallet and would like to add the eSVC thereto.The processor may add the activated eSVC to an e-wallet designated bythe user upon instruction by the user, or automatically according topreferences in the e-wallet which may be recognized in embodiments wherethe use purchases the eSVC from the user's e-wallet provider or inanother arrangement where the e-wallet provider may recognize thepurchase of the eSVC which needs to be automatically added to the user'se-wallet.

In certain embodiments (e.g., as reflected in FIGS. 9A-D) a user maycreate an e-wallet, establish rules for the e-wallet, provision thee-wallet, and access the e-wallet to facilitate electronic transactions.Suitable processes for registering the eSVC are disclosed inInternational Application Serial No. PCT/US13/26501, filed on Feb. 15,2013, and entitled “System and Method of Registering Stored-Value CardsInto Electronic Wallets.” Examples of techniques for authenticating,allocating, and provisioning an eSVC are described hereinbelow. Variousregistration, authentication, allocation, and provisioning techniquesmay be performed prior to use of the eSVC which would be recognized byone skilled in the art with the aid of this disclosure. For example, theuser may register the eSVC in one or more electronic wallets (e.g.,electronic wallet 10 of FIGS. 3A and 3B).

In an embodiment, the eSVC may be added to an e-wallet by receiving anintelligent code scan for an intelligent code on a physical stored-valuecard (e.g., as performed in block 20 of FIG. 1 ), requesting a securitykey associated with the physical stored-value card or securityinformation for an electronic wallet, adding the electronic-stored valuecard to an electronic wallet, receiving a security key for the physicalstored-value card, receiving the security information for the electronicwallet, displaying the balance of the electronic stored-value card,confirming the physical-stored value card is activated, or combinationsthereof. The intelligent code scan may comprise a URL, and the URL maycomprise a retailer identifier, a card number, a PIN, or combinationsthereof. The intelligent code scan may be obtained by scanning a dynamicintelligent code on the front or back of the physical stored-value card.The security key may comprise a PIN associated with the physicalstored-value card. The security information comprises login informationfor the electronic wallet.

After adding the eSVC to an e-wallet, flow may proceed to block 31 ofFIG. 1 ; alternatively, to block 30 of FIG. 1 .

At block 30 of FIG. 1 , an eSVC exchange service may be provided. Inembodiments, the eSVC exchange service may be provided (e.g., by theeSVC processor, a third-party eSVC exchange provider, the eSVC issuer,or combinations thereof) to the user, e.g., as a provider of an e-walletof the user. For example, the user may access the eSVC exchange servicevia a user device, and may select all or a portion of a pre-existingeSVC in the user's e-wallet to exchange for the new eSVC. The exchangeservice may then remove all or a portion of the pre-existing eSVC fromthe user's e-wallet and add the new eSVC to the user's e-wallet (e.g.,as described for block 29 of FIG. 1 ). Embodiments of an eSVC exchangeservice, where the value (e.g., in the form of currency, discount,promotion, points, rewards) of the eSVC is embodied as a value tokenwhich can be exchanged for other value tokens in the e-wallet, aredescribed hereinbelow for embodiments of the value token transactionprocessing systems. After providing an eSVC exchange service, flow mayproceed to block 29 of FIG. 1 ; alternatively, to block 31 of FIG. 1 .

At block 31 of FIG. 1 , the purchased and activated eSVC may be provided(e.g., by the processor of the eSVC, the issuer of the eSVC, or anentity which is both) to the user or a third-party recipient (e.g., as agift from the user). The eSVC may be provided (e.g., sent, received,delivered, fetched, acquired, presented, or combinations thereof) viavarious communication means, including SMS, email, video (e.g., YouTube,Vimeo, Skype, video message, or combinations thereof), instant message,a website, an online storage medium, a cloud storage system, other meansfor electronically obtaining the electronic stored-value card, orcombinations thereof. In embodiments where the eSVC is provided withoutan electronic wallet, the eSVC may be provided by making a communicationof the various types discussed above and/or by providing a link to usethe eSVC (e.g., in the form of a e-gift, discount, credit, promotionaloffer, or combinations thereof) available to the user (e.g., on the userdevice) via an online transaction portal. In embodiments where the eSVCis provided to the user via an electronic wallet, the eSVC may beprovided by making a communication of the various types discussed aboveand/or by providing a link to use the eSVC (e.g., in the form of ae-gift, discount, credit, promotional offer, or combinations thereof)available to the user (e.g., on the user device) via the electronicwallet.

The method in FIG. 2 starts at block 20. The method of FIG. 2 utilizes achit or a physical stored-value card, for example, located on an endcap.A physical retail location or online merchant portal may have a physicalor virtual “endcap” which is a display for the intelligent codes forvarious brands and/or values of eSVCs. The endcap may also have rackswhich hold one or more chits and/or physical stored-value cards. A chitmay comprise cardboard, plastic, or other material suitable for displayon an endcap. In embodiments, the chit may hang on a rack of the endcap.The chit may comprise an intelligent code, a barcode, or both. Inembodiments where the chit comprises a barcode, the intelligent code maybe displayed on the endcap display. In embodiments where the chitcomprises a barcode and intelligent code, the intelligent code may notbe displayed on the endcap display. A physical stored-value card maycomprise a card product as is known for credit cards, debit cards,loyalty cards, gift-cards, rewards cards, membership cards, promotionalcards, discount cards, etc. The physical stored-value card may comprisea n intelliegent code, for example, on the front or back of the physicalstored-value card.

In the method of FIG. 2 , blocks 20, 21, 22, and 23 are the same stepsof the method of blocks 20, 21, 22, and 23 of FIG. 1 , except that themethod of FIG. 2 utilizes chits and/or physical stored-value cards, forexample, located on an endcap, to provide eSVCs.

At block 20 of FIG. 2 , an intelligent code scan is received. Theintelligent code scan is associated with a request for an eSVC, arequest for a tutorial for obtaining the electronic stored-value cardvia a intelligent code scan, or both. That is, a request for an eSVC maybe received via a n intelligent code scan, a tutorial for obtaining theeSVC may be received via an intelligent code scan, or both may bereceived by one or more intelligent code scans. The intelligent code mayinclude information comprising retailer identification (e.g., store ID),eSVC brand, rack, eSVC category, application data known to those ofskill in the art with the aid of this disclosure, or combinationsthereof. In an embodiment, the intelligent code does not compriseinformation which can be used to redeem, activate, or use an electronicstored-value card. The tutorial may comprise the tutorial embodimentsdiscussed for block 20 of FIG. 1 .

A user may generally make the request for the eSVC at a physical retail(e.g., merchant) location, an online merchant portal, via a user device(e.g., user device 14 of FIGS. 3A and 3B), or combinations thereof. Aphysical retail location or online merchant portal may have a physicalor virtual endcap which displays the intelligent codes and barcodes forvarious brands and/or values of eSVCs. In embodiments, the endcap mayhave physical stored-value cards and/or chits (e.g., of cardboard orplastic) which have no magnetic stripe and/or value in themselves butwhich display the intelligent code, the barcode, or both. For example,the intelligent code may comprise a general intelligent code and bedisplayed on the endcap display itself, and the barcode may be unique tothe eSVC and displayed on the chit and/or physical stored value card(e.g., wherein the chit is placed on the endcap (e.g., via a rack) andcan be disposed of after purchase of the eSVC). In another example, theintelligent code may comprise a general or unique intelligent code andbe displayed on the chit and/or physical stored-value card which isplaced on the endcap (e.g., via a rack), and the barcode may be uniqueto the eSVC and likewise displayed on the chit (e.g., wherein the chitis placed on the endcap (e.g., via a rack) and can be disposed of afterpurchase of the eSVC). Because the physical endcap display uses chits inorder to sell eSVCs, distribution or manufacture costs of physical cardproducts is reduced.

At block 21 of FIG. 2 , an eSVC shopping cart is established. The eSVCshopping cart may be established in response to the received intelligentcode scan. The eSVC shopping cart may comprise a digital representationof a physical shopping cart used to buy goods or services (e.g., such asthe shopping carts commonly used on merchant websites to purchase goodsor services (e.g., a hotel website, an airline website, a bookstorewebsite, etc.). The eSVC shopping cart may comprise unactivated eSVCsassociated with the received intelligent code scan. For example, afteran eSVC processor receives the intelligent code scan from a user, theeSVC processor may create an eSVC shopping cart which stores theintelligent code information identifying the eSVC associated with theintelligent code. The eSVC shopping cart may also associate anyinformation captured in block 22 of the method of FIG. 2 with one ormore eSVCs therein. The eSVC in the eSVC shopping cart may comprise anunactivated state. For example, as a digital representation of the eSVCstatus on a device such as the user's mobile device, the eSVC shoppingcart may be shown as a webpage, popup window, app, or combinationsthereof, and the eSVC may be shown with a visual identifier such as alogo or icon (e.g., a Brand X logo if the eSVC is a Brand X eSVC). Thevisual identifier may be made transparent and/or without interactivityon the user's device to indicate the eSVC is in the eSVC shopping cartbut not yet activated. In embodiments, the eSVC shopping cart is notdisplayed to the user until the user purchases and activates the eSVC.

At block 22 of FIG. 2 , information may be captured in response to therequest for an eSVC. In addition to information contained in theintelligent code, captured information may comprise GPS coordinates ofthe user (e.g., of the user's mobile device), type of user device (e.g.,of the user's mobile device), identification of the user device, IPaddress, one or more email addresses, a requested value for the eSVC,whether the request is for multiple eSVCs, e-wallet account information(e.g., e-wallet login), loyalty program information (e.g., loyaltynumber, loyalty login information), where to deliver the eSVC (e.g., athird-party via communication means described herein), whether the userwishes to purchase now or later, whether the user wishes to purchasein-store or online, other information known to those skilled in the artwith the aid of this disclosure, or combinations thereof. Inembodiments, the user may be prompted on a device (e.g., a user device)and asked to submit the information which is desirably captured. Theuser may enter and submit the information, may deny entering theinformation, may request to enter the information later, may take noaction, or combinations thereof. In embodiments wherein the eSVCshopping cart has not been paused before capturing information andpausing the eSVC shopping cart is desired, flow may proceed from block22 to block 23 of FIG. 2 . In embodiments where the eSVC shopping carthas already been paused or pausing is not desired, flow from block 22 ofFIG. 2 may proceed to block 33 of FIG. 2 .

At block 23 of FIG. 2 , the eSVC shopping cart may be paused. Forexample, the provider of the eSVC shopping cart, e.g., the eSVCprocessor or the eSVC issuer, may pause further activity associated withthe eSVC shopping cart (in embodiments, other than adding more eSVCs viaintelligent code scan). In embodiments, activity associated with theeSVC shopping cart may be paused until a condition is satisfied, such asa purchase of an eSVC, an activation of an eSVC, or in one-stepactivation scenarios, the purchase and activation of the eSVC. Inembodiments where information is not captured before pausing the eSVCshopping cart and captured information is desired, flow proceeds toblock 22 of FIG. 2 . In embodiments where information has already beencaptured or is not desired, flow may proceed to block 33 of FIG. 2 .

At block 33 of FIG. 2 , a barcode scan is received. In embodiments, theuser may use a user device to scan the barcode (e.g., on the endcapdisplay or on the chit or on the physical stored-value card). Thebarcode may comprise an EAN128 barcode, a dynamic EAN128 barcode, or aUPC. In embodiments, the barcode may comprise activation informationwhich may comprise an activation code. In an embodiment, the barcodecomprises the activation information in an issuer account portion of thebarcode. Additionally the barcode may comprise a vendor productidentification in a vendor product identification portion of thebarcode. When the user scans the barcode, the information contained onthe barcode is transmitted to the eSVC processor, eSVC issuer, or aparty which is both the processor and issuer of the eSVC. Inembodiments, the user is not the merchant and thus is not anauthenticated party for which receipt of the barcode would triggerauthentication of the eSVC. In such embodiments, the party that receivesthe barcode scan (made by the user) may perform various activities withthe information contained in the received barcode scan, for example, asdescribed for block 34 of FIG. 2 .

At block 34 of FIG. 2 , the intelligent code scan is associated with thebarcode scan (e.g., by the eSVC processor, the eSVC issuer, or both). Inembodiments, the eSVC processor, the eSVC issuer, or a party that isboth the issuer and processor of the eSVC may associate the barcode scanwith the intelligent code scan. For example, the party may gather theinformation for preparation of purchase and activation of theunpurchased and/or unactivated eSVC in the eSVC shopping cartestablished in block 21 of FIG. 2 .

In the disclosed embodiments, the user may choose (e.g., via a promptembodied as a selection screen, popup window, which can be promptedwhile entering information at block 22 of FIG. 2 , etc.) to purchase theeSVC via in-store purchase (e.g., via a point-of-sale device) or via anonline payment portal (e.g., provided by a computer device of the eSVCprocessor which acts as an online merchant for the purchase of the eSVC,of a third-party merchant, or of an eSVC issuer which acts as an onlinemerchant for the purchase of the eSVC). For example, after receipt ofthe barcode scan from the user, the user may be prompted to purchase theeSVC by removing the chit/physical stored-value card from the endcap andtake the chit/physical stored-value card to a point-of-sale device ofthe merchant for purchase and/or activation of the eSVC. In analternative embodiment, after receipt of the barcode scan from the user,the user may be prompted to purchase the eSVC via an online paymentportal. In embodiments, the user may automatically be taken (e.g., afterthe barcode scan is received) to online payment unless the user electsnot to purchase online, or the eSVC may automatically be prepared (e.g.,after the barcode scan is received) (e.g., according to blocks 24 and 25of FIG. 1 ) for in-store purchase unless the user elects not to purchasein-store. In embodiments, the user may use a user device to request theonline purchase without need for a point-of-sale device, e.g., via anonline payment portal, or the user may use the user device to electin-store payment for the eSVC. If the user requests online payment,payment may be made according to the techniques described for block 26of FIG. 1 . If the user elects to pay in-store, the steps of block 24and/or block 25 of FIG. 1 may be performed depending on which entity(e.g., eSVC processor or eSVC issuer) provides the barcode andactivation information for the eSVC. In embodiments, the user may choosenot to purchase at the time of prompting, and the eSVC shopping cart mayremain paused as discussed in block 23 of FIG. 2 until further action istaken (e.g., in-store purchase of the eSVC, online purchase of the eSVC,deletion of the eSVC from the eSVC shopping cart, etc.).

At block 27 of FIG. 2 , a purchase verification is received. Thepurchase verification may comprise an activation request of the eSVC. Inembodiments where the user elects to purchase the eSVC in-store, theuser at the physical endcap at a merchant location may remove thechit/physical stored-value card from the endcap display and take thechit/physical stored-value card comprising the barcode to a merchantcomputer device (e.g., a point-of-sale device having a barcode scanner).The clerk of the merchant may scan the barcode on the chit/physicalstored-value card, and the processor of the eSVC or issuer of the eSVCmay receive the barcode scan again, albeit from the merchant'spoint-of-sale device. Scanning the barcode and activation information bythe merchant may be considered a one-step activation method, as opposedto a two-step activation method where the barcode and activationinformation are separately provided and purchase of the eSVC is aseparate step from activation of the eSVC. The one-step activation ofthe eSVC embodied by scanning the barcode and activation information maycomprise simultaneously or serially (e.g., one after another withoutseparate request) scanning the barcode and activation information (e.g.,comprising an activation code, a vendor product identification, anissuer account code, or combinations thereof) at a merchant computerdevice (e.g., point-of-sale terminal). One-step activation of the eSVConly requires a single entry by a clerk operating the point-of-saleterminal to activate the eSVC. For example, the one step may beperformed at the point-of-sale terminal by scanning the barcode, (e.g.,an EAN/UCC-128 barcode) comprising both a vendor product identificationportion and an issuer account portion. The vendor product identificationportion may be used to perform a look-up to determine eSVC identity andprice, or may contain the eSVC identity and price without need formerchant look-up. In embodiments, the price does not match the value ofthe eSVC, for example, when a promotional offer sells an eSVC of agreater value (e.g., $30) for a price of a lesser value (e.g., $20). Theissuer account portion may be used to activate the particular accountassociated with the eSVC such that the eSVC may be used (e.g., totransact business with a merchant). Upon being entered at thepoint-of-sale terminal, the issuer account portion may be conveyed (forexample, via a network described hereinbelow) to, and received by, theissuer of the eSVC (e.g., as a purchase verification and/or anactivation request); the issuer account portion may be conveyed (forexample, via a network described hereinbelow) to, and received by, theprocessor of the eSVC (e.g., as a purchase verification and/or as anactivation request); the issuer account portion may be conveyed (forexample, via a network described hereinbelow) to, and received by, athird-party eSVC processor responsible for activating the eSVC (e.g., asa purchase verification and/or as an activation request); orcombinations thereof. Once the purchase verification and/or activationrequest is received, the processor, issuer, third-party processor, orcombinations thereof, may activate the eSVC via methods known in the artwith the aid of this disclosure.

In embodiments with an online purchase of the eSVC, the barcode on thechit/physical stored-value card may not be scanned again (e.g., by themerchant via a point-of-sale device). In lieu of a second barcode scan(e.g., by the merchant), the user may choose to purchase the eSVC via anonline payment portal as described herein. In online purchaseembodiments, when the online payment portal requests payment information(e.g., account number, expiration date, security code) for a card otherthan the eSVC being purchased (e.g., a physical card, another eSVC, orcombination thereof), the user, e.g., via the user device, may enter thepayment information (e.g., card number (or another eSVC number), billingaddress (postal code), expiration date, security code, or combinationsthereof) and the payment information may be processed by the eSVCprocessor (in embodiments where the eSVC processor provides the paymentportal), or by a third-party merchant that forwards the paymentinformation to the eSVC processor. Upon online payment, a purchaseverification may be conveyed (for example, via a network describedhereinbelow) to, and received by, the issuer of the eSVC (e.g., as apurchase verification and/or an activation request); the purchaseverification may be conveyed (for example, via a network describedhereinbelow) to, and received by, the processor of the eSVC (e.g., as apurchase verification and/or as an activation request); the purchaseverification may be conveyed (for example, via a network describedhereinbelow) to, and received by, a third-party eSVC processorresponsible for activating the eSVC (e.g., as a purchase verificationand/or as an activation request); or combinations thereof.

Once the purchase verification and/or activation request is received,the processor, issuer, third-party processor, or combinations thereof,may activate the eSVC via methods known in the art with the aid of thisdisclosure. In embodiments, the purchase of the eSVC may be processed bythe provider of the eSVC and/or e-wallet (e.g., via eSVC processor), bya merchant, by the eSVC issuer, or combinations thereof. In anembodiment, the purchase may be processed by applying a purchase valueto complete the transaction. In an embodiment, to process the purchase,authentication information to process the purchase may be identified, avalue associated with the eSVC (e.g., embodied as a value token,described below) may be assigned, at least a portion of the value ofanother eSVC (e.g., value token) may be applied to at least a portion ofthe purchase price, at least a portion of the value of a physical cardmay be applied to at least a portion of the purchase price, orcombinations thereof. In an embodiment, identifying authenticationinformation may comprise authentication techniques known to thoseskilled in the art with the aid of this disclosure. In embodiments,processing the purchase may further comprise processing at least aportion of the purchase in a primary wallet of an e-wallet (e.g.,electronic wallet 10 of FIG. 3A), processing at least a portion of thepurchase in a sub-wallet of an e-wallet (e.g., of electronic wallet 10of FIG. 3A), or both. In embodiment, a notification may be sent to theuser, merchant, processor, and or issuer that the purchase has beenprocessed. After performing an embodiment of the step at block 27 ofFIG. 2 , flow may proceed to block 28 of FIG. 2 .

At block 28 of FIG. 2 , the eSVC shopping cart is unpaused. Inembodiments, the eSVC shopping cart is unpause after purchase of an eSVCcontained therein, after activation of an eSVC therein, or both. Inembodiments, the eSVC shopping cart is unpaused only for the eSVCpurchased and/or activated while the eSVC shopping cart remains pausedfor non-purchased and/or unactivated eSVCs. Flow may proceed to block 29of FIG. 2 ; alternatively, to block 30 of FIG. 2 ; alternatively toblock 31 of FIG. 2 .

At block 29 of FIG. 2 , the purchased and activated eSVC may be added toan electronic wallet (e.g., of the user). As used herein, an “electronicwallet” (also referred to as “e-wallet”) may include an electronicallymaintained data file (e.g., maintained on a computer device of aprovider of the electronic wallet, for example, the eSVC processor)which may comprise pre-existing eSVCs, authentication information, rulesfor use, sub-wallets (e.g., for separately maintaining eSVC-relatedinformation), and electronic value tokens (e.g., electronicrepresentations of the monetary and/or other value associated with theelectronic stored-value card-related information contained in thee-wallet/sub-wallet). The eSVC processor may prompt the user (e.g.,before or after activation of the eSVC) whether the user would like tocreate an electronic wallet and add the eSVC thereto, or whether theuser has a pre-existing e-wallet and would like to add the eSVC thereto.The processor may add the activated eSVC to an e-wallet designated bythe user upon instruction by the user, or automatically according topreferences in the e-wallet which may be recognized in embodiments wherethe use purchases the eSVC from the user's e-wallet provider or inanother arrangement where the e-wallet provider may recognize thepurchase of the eSVC which needs to be automatically added to the user'se-wallet.

In certain embodiments (e.g., as reflected in FIGS. 9A-D) a user maycreate an e-wallet, establish rules for the e-wallet, provision thee-wallet, and access the e-wallet to facilitate electronic transactions.Suitable processes for registering the eSVC are disclosed inInternational Application Serial No. PCT/US13/26501, filed on Feb. 15,2013, and entitled “System and Method of Registering Stored-Value CardsInto Electronic Wallets.” Examples of techniques for authenticating,allocating, and provisioning an eSVC are described hereinbelow. Variousregistration, authentication, allocation, and provisioning techniquesmay be performed prior to use of the eSVC which would be recognized byone skilled in the art with the aid of this disclosure. For example, theuser may register the eSVC in one or more electronic wallets (e.g.,electronic wallet 10 of FIGS. 3A and 3B).

In an embodiment, the eSVC may be added to an e-wallet by receiving anintelligent code scan for an intelligent code on a physical stored-valuecard (e.g., as performed in block 20 of FIG. 2 ), requesting a securitykey associated with the physical stored-value card or securityinformation for an electronic wallet, adding the electronic-stored valuecard to an electronic wallet, receiving a security key for the physicalstored-value card, receiving the security information for the electronicwallet, displaying the balance of the electronic stored-value card,confirming the physical-stored value card is activated, or combinationsthereof. The intelligent code scan may comprise a URL, and the URL maycomprise a retailer identifier, a card number, a PIN, or combinationsthereof. The intelligent code scan may be obtained by scanning a dynamicintelligent code on the front or back of the physical stored-value card.The security key may comprise a PIN associated with the physicalstored-value card. The security information comprises login informationfor the electronic wallet.

After adding the eSVC to an e-wallet, flow may proceed to block 31 ofFIG. 2 ; alternatively, to block 30 of FIG. 2 .

At block 30 of FIG. 2 , an eSVC exchange service may be provided. Inembodiments, the eSVC exchange service may be provided (e.g., by theeSVC processor, a third-party eSVC exchange provider, the eSVC issuer,or combinations thereof) to the user, e.g., as a provider of an e-walletof the user. For example, the user may access the eSVC exchange servicevia a user device, and may select all or a portion of a pre-existingeSVC in the user's e-wallet to exchange for the new eSVC. The exchangeservice may then remove all or a portion of the pre-existing eSVC fromthe user's e-wallet and add the new eSVC to the user's e-wallet (e.g.,as described for block 29 of FIG. 2 ). Embodiments of an eSVC exchangeservice, where the value (e.g., in the form of currency, discount,promotion, points, rewards) of the eSVC is embodied as a value tokenwhich can be exchanged for other value tokens in the e-wallet, aredescribed hereinbelow for embodiments of the value token transactionprocessing systems. After providing an eSVC exchange service, flow mayproceed to block 29 of FIG. 2 ; alternatively, to block 31 of FIG. 2 .

At block 31 of FIG. 2 , the purchased and activated eSVC may be provided(e.g., by the processor of the eSVC, the issuer of the eSVC, or anentity which is both) to the user or a third-party recipient (e.g., as agift from the user). The eSVC may be provided (e.g., sent, received,delivered, fetched, acquired, presented, or combinations thereof) viavarious communication means, including SMS, email, video (e.g., YouTube,Vimeo, Skype, video message, or combinations thereof), instant message,a website, an online storage medium, a cloud storage system, other meansfor electronically obtaining the electronic stored-value card, orcombinations thereof. In embodiments where the eSVC is provided withoutan electronic wallet, the eSVC may be provided by making a communicationof the various types discussed above and/or by providing a link to usethe eSVC (e.g., in the form of a e-gift, discount, credit, promotionaloffer, or combinations thereof) available to the user (e.g., on the userdevice) via an online transaction portal. In embodiments where the eSVCis provided to the user via an electronic wallet, the eSVC may beprovided by making a communication of the various types discussed aboveand/or by providing a link to use the eSVC (e.g., in the form of ae-gift, discount, credit, promotional offer, or combinations thereof)available to the user (e.g., on the user device) via the electronicwallet.

FIG. 3A is a schematic illustration of an embodiment of a systemaccording to the disclosure. As shown in FIG. 3A, an embodiment of thedisclosed system for providing an electronic stored-value card via anintelligent code scan may comprise a processor computer device 12 (e.g.,of an eSVC processor), a user device 14 (e.g., of a user), orcombinations thereof.

The components of the system of FIG. 3A may be operably connected viaone or more networks (e.g., broadband, optical, Wi-Fi, Bluetooth, NFC,cellular, satellite, cloud, card processing network, banking network, alocal area network, the World Wide Web for Internet, non-cellular mobilephone network, a land-line network, Public Switched Telephone Network(PSTN), a dedicated communication line, other networks for transferringelectronic information, or combinations thereof). Particularly, the userdevice 14 may be operably connected to the processor computer device 12via the network, and vice-versa.

The user device 14 may comprise a personal computer, a tablet, asmartphone, a cloud computing system, a server, or combinations thereof.The device used by the user or consumer to purchase the eSVC may be thesame or different device from the user device 14. In an embodiment, theuser may scan a QR code for an eSVC using the user device 14. In anadditional or alternative embodiment, the user may scan a barcode for aneSVC using the user device 14. In an additional or alternativeembodiment, the user or consumer may purchase an eSVC using the userdevice 14 (e.g., via an online payment portal). In additional oralternative embodiments, the user may enter information required orrequested for the purchase of an eSVC using the user device 14.

The processor computer device 12 may have any suitable configuration forperforming the functions disclosed herein (e.g., a personal computer, atablet, a smartphone, a cloud computing system, a server, orcombinations thereof). The processor computer device 12 may be acomputer device of an eSVC processor, and in additional embodiments, aprovider of one or more electronic wallets (e.g., electronic wallet 10),a provider of an eSVC (e.g., eSVC 11), or both.

FIG. 3A shows the processor computer device 12 may comprise anelectronic wallet 10. In embodiments, the processor computer device 12may further comprise an electronic value token transaction processingsystem, for example, of an embodiment described in FIGS. 4A-B, and 5A-Chereinbelow. In embodiments, the processor computer device 12 mayfurther comprise a database (e.g., database/datastore 180 as describedfor the figures hereinbelow) to store one or more eSVCs (e.g., eSVC 11),one or more electronic wallets (e.g., electronic wallet 10), at least aportion of the information associated with each eSVC (intelligent codeinformation, barcode information, captured information from a user, orcombinations thereof), or combinations thereof.

FIG. 3A shows an embodiment of the system comprising one electronicwallet 10. In alternative embodiments, the system may comprise a firstelectronic wallet and a second electronic wallet. In additional oralternative embodiments, the electronic wallet 10 may comprise anynumber of sub-wallets as described herein below. Electronic wallets(e.g., electronic wallet 10) may offer a variety of services, includingstoring, managing, and facilitating the redemption of value (e.g.,monetary, discount, promotional, value tokens, rewards, etc.) of eSVCs.One or more eSVCs (e.g., eSVC 11) may be associated (e.g., registered)with the one or more electronic wallets. For example, a first eSVC(e.g., eSVC 11) and a second eSVC may be registered in electronic wallet10. Alternatively, a first eSVC (e.g., eSVC 11) may be registered in afirst electronic wallet and a second eSVC may be registered in a secondelectronic wallet. In additional or alternative embodiments, one or moreeSVCs may be associated (e.g., registered) in a sub-wallet of anelectronic wallet (registration techniques, methods, and processes arediscussed hereinbelow). Embodiments of the electronic wallet 10 aredescribed in detail hereinbelow, for example, in the discussion for FIG.4B.

FIG. 3A also shows an embodiment of the processor computer device 12comprising an online payment portal.

The processor computer device 12 is configured to accomplish theembodiments of the methods disclosed hereinabove. In embodiments, theprocessor computer device 12 of FIG. 3A is configured to a receive arequest for an electronic stored value card via an intelligent codescan; to receive a purchase verification for the electronic stored-valuecard; to provide the electronic stored-value card; to provide a barcode,an activation information, or both of the electronic-stored value cardin response to the request for an electronic stored-value card; toobtain the barcode, the activation information, or both from an issuerof the electronic stored-value card in response to the request for anelectronic stored-value card; to receive a barcode scan for theelectronic stored-value card from a user device, and associate theintelligent code scan with the barcode scan; to receive a barcode scanfor the electronic stored-value card from a merchant computer device,and to activate the electronic stored-value card; to establish anelectronic stored-value card shopping cart upon receipt of theintelligent code scan, wherein the electronic stored-value card isplaced in the electronic stored-value card shopping cart; to pause theelectronic stored-value card shopping cart; to unpause the electronicstored-value card shopping cart; to add the electronic stored-value cardto an electronic wallet; to capture information as described for block22 in FIGS. 1 and 2 (e.g., comprising a user email, a retaileridentification, a card brand, a GPS location, a device type, a deviceidentification, an IP address, a rack, a category, or combinationsthereof); to provide an online payment portal for the electronicstored-value card; to provide an electronic stored-value card exchangeservice for the electronic stored-value card, or combinations thereof.

In embodiments, the processor computer device 16 may be configured toprocess at least a portion of an eSVC purchase via a primary wallet ofan electronic wallet 10, the merchant computer device 16 may beconfigured to process at least a portion of an eSVC purchase via asub-wallet of an electronic wallet 10, or both (primary wallets andsub-wallets are discussed hereinbelow).

The processor computer device 12 may be configured to perform otherfunctions as described above for the methods in FIGS. 1 and 2 .

In the system of FIG. 3A, a user may initiate the purchase of an eSVCvia an intelligent code scan. The user may then proceed to purchase theeSVC via online purchase, whether or not a chit or physical stored-valuecard is used.

In the system of FIG. 3A, a user may input an intelligent code with userdevice 14, which is sent automatically or via instruction from the userto the processor computer device 12. The processor computer device 12may then establish an eSVC shopping cart for the eSVC associated withthe intelligent code. The processor computer device 12 may then promptthe user for information to be entered via user device 14, may pause theeSVC shopping cart, or both. The user may use the user device 14 tocommunicate with the processor computer device 12 with the user'spreferred payment method or if the user would like to not make apurchase. The user may decide to purchase the eSVC associated with theintelligent code. In the system embodiment of FIG. 3A, the user maypurchase the eSVC via an online payment portal 13 provided by theprocessor computer device 12. As described above, the user may go to theonline payment portal and enter requested information (e.g., cardnumber, expiration date, security code, billing information) to completethe purchase of the eSVC. The processor computer device 12 may thenunpause the eSVC shopping cart upon receipt of a purchase verification.The processor computer device 12 may activate the eSVC upon receipt ofthe purchase verification. The processor computer device 12 may then addthe eSVC to an e-wallet of the user, exchange the eSVC for another eSVCin an e-wallet of the user, provide the eSVC to the user device 14 orotherwise, or combinations thereof. In embodiments utilizing a chit or aphysical stored-value card with a barcode as described hereinabove, theuser device 14 may scan the barcode of the eSVC, and the processorcomputer device 12 may receive the barcode scan and associate theintelligent code scan with the barcode scan, for example, to prepare theeSVC for purchase and activation in the eSVC shopping cart.

FIG. 3B is a schematic illustration of another embodiment of a systemaccording to the disclosure, shown a merchant computer device separatefrom the processor computer device. As shown in FIG. 3B, an embodimentof the disclosed system for providing an electronic stored-value cardvia an intelligent code scan may comprise a processor computer device 12(e.g., of an eSVC processor), a user device 14 (e.g., of a user), amerchant computer device 16 (e.g., of a merchant), an issuer computerdevice 18 (e.g., of an issuer of an eSVC), or combinations thereof.

The processor computer device 12 comprises a device separate from theissuer computer device 18, the merchant computer device 16, and the userdevice 14. In alternative embodiments, the processor computer device 13may comprise a device which is the same device as merchant computerdevice 16, the issuer computer device 18, or both (as shown in FIG. 3A).While FIG. 3B shows one embodiment of a system according to thedisclosure, it should be understood many system embodiments aredisclosed. For example, many system embodiments may accomplish theembodiments of the methods for providing an electronic stored-value cardvia an intelligent code disclosed hereinabove depending upon whetherprocessor computer device 12 comprises the same or different computerdevice as the merchant computer device 16 and/or issuer computer device18.

The components of the system of FIG. 3B may be operably connected viaone or more networks (e.g., broadband, optical, Wi-Fi, Bluetooth, NFC,cellular, satellite, cloud, card processing network, banking network, alocal area network, the World Wide Web for Internet, non-cellular mobilephone network, a land-line network, Public Switched Telephone Network(PSTN), a dedicated communication line, other networks for transferringelectronic information, or combinations thereof). Particularly, theprocessor computer device 12 may be operably connected to the userdevice 14, the merchant computer device 16, the issuer computer device18, or combinations thereof, via the network; the user device 14 may beoperably connected to the processor computer device 12, the merchantcomputer device 16, the issuer computer device 18, or combinationsthereof, via the network; the merchant computer device 16 may beoperably connected to the user device 14, the processor computer device12, the issuer computer device 18, or combinations thereof, via thenetwork; the issuer computer device 18 may be operably connected to theuser device 14, the processor computer device 12, the merchant computerdevice 16, or combinations thereof; or combinations thereof. When any ofthe computer devices 14, 16, or 18 of the system of FIG. 3B is operablyconnected to the processor computer device 12, said devices 14, 16, or18 may additionally be operably connected to an e-wallet on theprocessor computer device 12.

The processor computer device 12 of FIG. 3B may comprise one of theembodiments of the processor computer device 12 of FIG. 3A.

The user device 14 of FIG. 3B may comprise one of the embodiments of theuser device 14 described for FIG. 3A.

As seen in FIG. 3B, the merchant computer device 16 may comprise acomputer device (e.g., a point-of-sale device of a merchant) separatefrom the processor computer device 12. The merchant computer device 16may have any suitable configuration for performing the functionsdisclosed herein (e.g., a personal computer, a tablet, a smartphone, acloud computing system, a server, or combinations thereof). Inembodiments, the merchant computer device 16 may perform transactionswith a computer device (e.g., user device 14) of a consumer, forexample, in a purchase of an eSVC. The merchant computer device 16 maycommunicate with the processor computer device 12 to complete atransaction with a user or consumer.

In embodiments, the merchant computer device 16 may be configured toprovide an online payment portal, scan a barcode of an eSVC (e.g., eSVC11) (e.g., displayed on a chit or on the user device 14), to communicatewith the processor computer device 12 and/or issuer computer device 18to process an eSVC purchase, or combinations thereof.

As can be seen in FIG. 3B, the issuer computer device 18 may comprise acomputer device separate from the processor computer device 12. Theissuer computer device 18 may comprise a computer device of an issuer ofan electronic stored-value card (e.g., eSVC 11). The issuer computerdevice 19 may have any suitable configuration for performing thefunctions disclosed herein (e.g., a personal computer, a tablet, asmartphone, a cloud computing system, a server, or combinationsthereof). The issuer computer device 18 may be configured to generate abarcode for an eSVC (e.g., eSVC 11), to retrieve a pre-generated barcodefor an eSVC, to provide a barcode for an eSVC to the processor computerdevice 12, to provide a barcode for an eSVC to the user device 14, orcombinations thereof.

In the system of FIG. 3B, a user may initiate the purchase of an eSVCvia an intelligent code scan. The user may then proceed in two paths topurchase, one for embodiments without a chit or physical stored-valuecard, and one for embodiments with a chit comprising a barcode or aphysical stored-value card with a transmittable indicia.

In embodiments without a chit or a stored-value card, a user may scan anintelligent code with user device 14, which is sent automatically or viainstruction from the user to the processor computer device 12. Theprocessor computer device 12 may then establish an eSVC shopping cartfor the eSVC associated with the intelligent code. The processorcomputer device 12 may then prompt the user for information to beentered via user device 14, may pause the eSVC shopping cart, or both.The user may use the user device 14 to communicate with the processorcomputer device 12 with the user's preferred payment method or if theuser would like to not make a purchase. The user may decide to purchasethe eSVC associated with the intelligent code. The user may purchase theeSVC via an online payment portal 13 or via a merchant computer device16 (e.g., a point-of-sale device). If the user elects an onlinepurchase, the user may make a payment as discussed in the system of FIG.3A and the methods hereinabove. If the user elects an in-store purchase,the processor computer device 12 may provide a barcode and/or activationinformation to the user device 14, and the user device 14 is configuredto display the barcode (e.g., via a screen of a mobile device). In anembodiment, the processor computer device 12 may communicate withanother device (e.g., issuer computer device 18) to obtain the barcodeand activation information of the eSVC 11. The user may then scan (orhave scanned) the barcode displayed on the user device 14 with themerchant computer device 16 to make the purchase of the eSVC. Thepurchase is processed as described hereinabove (e.g., by processorcomputer device 12), and a payment verification is received by theprocessor computer device 12. The processor computer device 12 may thenunpause the eSVC shopping cart. The processor computer device 12 maythen add the eSVC to an e-wallet of the user, exchange the eSVC foranother eSVC in an e-wallet of the user, provide the eSVC to the uservia user device 14 or otherwise, or combinations thereof.

In embodiment using a chit or physical stored-value card, the user mayscan anb intelligent code with user device 14, which is sentautomatically or via instruction from the user to the processor computerdevice 12. The processor computer device 12 may then establish an eSVCshopping cart for the eSVC associated with the intelligent code. Theprocessor computer device 12 may then prompt the user for information tobe entered via user device 14, may pause the eSVC shopping cart, orboth. The user may use the user device 14 to communicate with theprocessor computer device 12 with the user's preferred payment method orif the user would like to not make a purchase. The user may decide topurchase the eSVC associated with the intelligent code. The processorcomputer device 12 may instruct the user to scan the barcode on thechit/physical stored-value card with the user device 14, or the chit (orphysical stored-value card) or endcap may display instructionsinstructing the user to do so. Once the user scans the barcode with theuser device 14, the processor computer device 12 associates theintelligent code scan with the barcode scan, for example, to prepare theeSVC in the eSVC shopping cart for activation. The processor computerdevice 12, the endcap, the chit (or physical stored-value card), orcombinations thereof, may instruct the user to remove the chit (orphysical stored-value card) from the endcap display and to scan (or havescanned) the chit (or physical stored-value card) at a point-of-saledevice of a merchant (e.g., merchant computer device 16). The purchaseis processed as described hereinabove (e.g., by processor computerdevice 12), and a payment verification is received by the processorcomputer device 12. The processor computer device 12 may then unpausethe eSVC shopping cart. The processor computer device 12 may then addthe eSVC to an e-wallet of the user, exchange the eSVC for another eSVCin an e-wallet of the user, provide the eSVC to the user via user device14 or otherwise, or combinations thereof.

The system and method embodiments disclosed hereinabove present variousbenefits and advantages. First, the cost of manufacturing anddistributing physical card products is reduced or eliminated. Second,merchants can sell physical card products as well as eSVCs as describedhereinabove, for example, when the physical cards are out of stock, orin addition to the physical card products. Third, the user of thesystems and methods can be presented with a list of available eSVCs uponscanning an intelligent code, thus, expanding the inventory of amerchant without additional inventory cost. Fourth, the user of thesystems and methods disclosed hereinabove has multiple payment methodsfrom which to choose, e.g., an in-store purchase, an online purchase, ora purchase at a later time in-store or online because of the establishedeSVC shopping cart. Fifth, with the use of intelligent codes, data canbe tracked and mined for user behavior, product popularity, conversionof eSVCs in an eSVC shopping cart to actual purchases, productinventory, types of user devices which utilize intelligent codes, etc.,and providing empowering business decisions based on user behavior andproduct performance (e.g., even in real-time data assessment scenarios).

In embodiments of the disclosed system, the intelligent codes may applyto single eSVCs, categories of eSVCs, or an entire catalogue of eSVCs.Moreover, in embodiments of the disclosed systems and methods, theintelligent codes may also be employed and/or utilized to activate,load, reload, and/or deliver other digital content, e.g., music, video,rewards, awards, etc.

As described above, the disclosed systems and methods may involve combocodes wherein the intelligent code represents multiple independenteSVCs. When the combo code is interpreted, the data associated with thecombo code, along with an activation or deactivation request, iscommunicated. Upon receipt of the combo code activation or deactivationrequest, the system retrieves pre-stored information from a databasecontaining eSVCs associated with specific combo codes.

In embodiments of the disclosed system, essentially any token or mediathat can be read by a point of sale and used for the activation/load,reload or delivery of digital content may serve to initiate and/orauthorize the disclosed methods and systems (e.g., existing loyaltycards, proxy cards, drivers licenses, etc.).

In embodiments of the disclosed systems and methods, the systems andmethods also provide a payment acceptance mechanism to convert In-Store(physical payment) to payment for any pending or partial paymenttransaction (e.g., pay for a Kohls.com order at Safeway point of sale).

In embodiments of the disclosed systems and methods, the systems andmethods also provide consumers with opportunity to sign up for freeoffers, wherein the free offers are provided with a purchase byvalidating transaction with the intelligent code system.

In embodiments of the disclosed systems and methods can be used or forthe direct benefit of the user of the system and methods.

Also disclosed herein (e.g., as shown in FIGS. 4A, 5A-B, and 7A-B), anelectronic value token transaction processing system provides users,merchants, vendors, issuers, providers, and other interested parties anefficient, secure, and effective system for facilitating theorganization, management, transportation, storage, and use of theaforementioned e-wallets and electronic value tokens in financialtransactions. As described hereinbelow, there are certain basic conceptsand functions employed by e-wallets and e-wallet enabled systems. Theseconcepts include the creation of an e-wallet, provisioning the e-wallet(e.g., converting tangible cards into electronic value tokens andassociating the electronic value tokens to an e-wallet or requesting anelectronic value token be associated with the e-wallet), accessing thee-wallet, and establishing rules for the e-wallet's use. Moreover, aswill be more fully detailed herein, the e-wallet may be used in a systemwherein the e-wallet provider manages the entirety of the e-wallet'scontents (e.g., the primary e-wallet, any sub-wallets or secondarywallets, and associated electronic value tokens therein). Alternatively,the e-wallet may be used in a system wherein the e-wallet providermanages only a portion of the e-wallet's contents (e.g. the primarye-wallet and electronic value tokens therein) and delegates themanagement of one or more (or all) sub-wallets or secondary wallets to athird-party's electronic value token transaction processing system. Aswill be further detailed herein, either of the two described managementsystems may be configured to allow the systems' user to fully manage thefunctionalities of the user's e-wallet; participate in value added/bonusprograms offered by issuers, vendors, and/or other electronic valuetoken-related parties; participate in card exchange activities (e.g.,wherein a user exchanges an electronic value token maintained in itse-wallet for an electronic value token not in the e-wallet); andparticipate in savings programs offered by issuers, vendors, and/orother electronic value token-related parties.

FIG. 4A illustrates an exemplary electronic value token transactionprocessing system 100. Specifically, FIG. 4A illustrates an electronicvalue token transaction computer 150 configured for communication withpoint of sale devices 111, one or more authorization systems 160 (e.g.,retailer, bank, and credit card), and datastore 180. Moreover, FIG. 4Aillustrates that the point of sale devices 111 are in communication witha proxy card 200 (which will be shown below to represent an embodimentof a means for a user to access an e-wallet) and that the datastore 180comprises an e-wallet unit 199, which in turn comprises e-wallets 10.

FIG. 4B illustrates an electronic wallet 10 in accordance with oneembodiment, and it is to be understood that the details of e-wallet 10may be employed in any of the various embodiments disclosed herein(e.g., as e-wallet 10 of FIGS. 4A, 5A, and 5B) and the maintenance ofsaid e-wallet 10 may be wholly performed by a single e-wallet system(e.g., electronic value token transaction processing system 100) or maydistributed across multiple e-wallet systems (e.g., electronic valuetoken transaction processing systems 1100 and 1200 and E-WalletAggregator System 1000). Specifically, FIG. 4B illustrates an electronicwallet 10 comprising authentication information 801, rules 802,electronic value tokens 804, sub-wallet 807 for credit card electronicvalue tokens, sub-wallet (with corresponding rules 817 and electronicvalue tokens 827), sub-wallet 808 for debit card electronic value tokens(with corresponding rules 818 and electronic value tokens 828), andsub-wallet 809 for stored-value card electronic value tokens (withcorresponding rules 819 and electronic value tokens 829). FIGS. 4A and4B may be further understood from the below discussion.

In order to eliminate the increasing complexity in organization,transport, security, and redemption, transaction cards are storedelectronically as value tokens in electronic wallets. As used herein, avalue token refers to an electronic identifier that may be used totransact business with a party willing to accept the electronic valuetoken, for example as tender for a purchase. Examples of such valuetokens include electronic representations of, or associated with, storedvalue cards (also referred to as prepaid cards) and other physicalrepresentations of value of a variety of types such as credit cards,debit cards, gift cards, prepaid telephone cards, loyalty cards,membership cards, tickets or ticket cards, entertainment cards, sportscards, prepaid cards, coupons, admission passes, prepaid orpre-purchased goods or services, and the like. In an embodiment, a valuetoken includes cash or currency. In an embodiment, the electronic valuetoken includes a credit or debit card or account. In an embodiment, avalue token includes a preexisting account such as a merchant account,bank account, etc. In an embodiment, a value token includes amerchant-issued and/or accepted credit, points, coupon or promotionalvalue. In an embodiment, a value token is associated with a prepaid cardor account, and unless otherwise indicated it is to be understood thatthe various embodiments described herein may be carried out in thecontext of a prepaid card or account such as a merchant gift card.

A physical credit card, debit card, stored-value card, or other physicalrepresentations of value may be converted into a value token to be addedto the electronic wallet. For example, physical gift cards or otherphysical representations of value may be transformed into value tokensin a user's electronic wallet via a point-of-sale device, cellularphone, a computer, short messaging service (“SMS”), and the like. Onceso transformed, the electronic value tokens may be redeemed by the user,after authentication, without possession of the physical representationsuch as gift cards by accessing the user's electronic wallet duringpurchase. In this way, the use of the term value token herein refers toelectronic representations and physical representations that can betransformed into electronic representations. In at least one embodiment,the physical gift card is inoperative after transformation. In analternative embodiment, the physical gift card is inoperative afterredemption of the electronic value token using the electronic wallet orthe physical gift card

Consumer use of value tokens typically involves a vendor, a redeemingmerchant or retailer, and an issuer. In various embodiments, the vendor,redeeming merchant, and issuer may be the same, different, or relatedentities. The point of sale where value tokens are purchased orotherwise made available for inclusion in an electronic wallet may bereferred to as the vendor. Thus, the vendor sells the electronic valuetokens themselves although the electronic value tokens may be redeemedat another place of business. An entity that will accept a value tokenfor business transactions, for example as tender for a purchase, may bereferred to as a redeeming merchant or retailer. For example, a grocerystore may sell the electronic value token of an apparel store. Thegrocery store is the vendor and the apparel store is the redeemingmerchant or retailer. An entity that provides the financial backingand/or payment processing for a given value token such as a prepaid cardor account may be referred to as the issuer. Issuers include directissuers of value tokens such as store-branded value tokens (e.g., storebranded prepaid cards or tokens issued directly by the merchant,sometimes referred to as closed-loop prepaid cards), and in someembodiments the vendor may also be the issuer and/or the redeemingmerchant (e.g., a prepaid card or token issued, sold, and redeemed bythe same merchant). Issuers also include financial institutions such asbanks, VISA, MasterCard, American Express, etc., and value tokens issuedby such institutions may be readily accepted by a number of redeemingmerchants to conduct transactions such as purchases (sometimes referredto as open loop prepaid cards or tokens since they may be redeemed at anumber of different merchants). Issuers may also be the providers ofbranded electronic wallets such as Google, Facebook, Twitter, and thelike, and in some embodiments such branded wallet contains value tokensassociated with the issuer (e.g., Google “cash” or credits, Pay Palcurrency, Facebook electronic currency, etc.) and may contain or beassociated with a sub-wallet containing gift card-related value tokens,a sub-wallet containing credit card-related value tokens, a sub-walletcontaining debit card-related value tokens, or a combination thereof.

Generally, an electronic value token transaction computer 150 credits ordebits (or takes other actions of the type described herein) theaccounts associated with the electronic value tokens contained within anelectronic wallet or sub-wallet. The electronic value token transactioncomputer 150 may generate or forward messages to authorization systems160 so that the authorization systems 160 can credit or debit (or takeother action of the type described herein) the accounts associated withthe electronic value tokens. Confirmation messages are returned to theelectronic value token transaction computer 150 and POS device 111, andthe electronic wallet 10 or a sub-wallet is updated as necessary.

In at least one embodiment, transaction information is separate fromauthentication information. For example, information about a purchaseitem, purchase price, purchase location, etc. is considered transactioninformation and is separate from authentication information such as anauthentication token, PIN, account number, etc. Among other things,keeping the information separate allows for separate processing androuting, allowing for greater efficiency and privacy. For example, inapplying the electronic value tokens according to the configurable rule,the priority may be based on a transaction information variables such asphysical location of a retailer originating the electronic walletrequest; transaction amount; type of retailer; time of day; day of week;week of month; month of year; department of retailer originating theelectronic wallet request; lane of retailer originating the electronicwallet request; identification of checker; parent company of a retaileroriginating the electronic wallet request; value of value tokens; andtype of the electronic wallet request in various embodiments. Suchtransaction and/or authentication information may be used by the systemsdescribed herein in conjunction with rules based decision making (e.g.,checking such transaction data to validate and apply a promotionassociated with the transaction), for security purposes (e.g., checkingsuch transaction data against pre-determined profiles to assist withfraud detection), and the like.

In at least one embodiment, the wallet provider stands in for thepurchaser, and redemption of the electronic value token occurs after thepurchase. However, this time mismatch creates a discrepancy in theretailer's records. Specifically, the retailer records a transactionbetween the retailer and the wallet provider. The retailer records alater redemption via value token, seemingly for no purchase. In theseinstances, a third party administrator is required that can connect theredemption with the transaction.

There can be many ways to provision or add value tokens to an electronicwallet. For example, a user may pay the vendor for a value token, andthe vendor may insert the electronic value token into the user's wallet.Alternatively, the user may obtain a physical representation of theelectronic value token from the vendor (e.g., a card, chit, printedreceipt, etc.) and may subsequently add the value to the electronicwallet (for example, via a phone or internet accessed user interface).The user may have a choice of many different retailers affiliated withthe vendor. In other words, a given vendor may offer a plurality oftokens associated with different retailers. For example, a retailer mayoffer promotions to compete for the user's business when purchasing avalue token such as a prepaid account.

Each retailer may mandate a specific format for value tokens. Forexample, one retailer may require a 16 digit card number plus a 4 digitmonth/year expiration date. Other retailers may require pin numbers,access numbers, card verification value numbers, card security codenumbers, and the like. Each piece of information for different retailersmay have a different format as well as a different name. As such, anelectronic wallet provider or host (for example, a primary e-walletprovider) would benefit by allowing third party administration forelectronic representations of value tokens have a variety of formatssuch as stored value cards, credit cards, debit cards, loyalty andpromotion cards, and other subsets of value tokens for whichadministration by the primary e-wallet provider would be more expensive.

In an embodiment, value tokens associated with prepaid cards or accountsmay be associated with a sub-wallet within the electronic wallet (forexample, a sub-wallet of a primary, branded electronic wallet such as aGoogle electronic wallet), and a third party may administer thesub-wallet on behalf of the primary/principal electronic wallet host orprovider. For example, during a transaction involving value tokensassociated with prepaid cards or accounts (e.g., electronic or virtualstored value cards), the provider of the electronic wallet allows asub-wallet associated with such value tokens to take control of aportion of the transaction, sometimes referred to as a sub-transaction.In an embodiment, a sub-transaction comprises a transaction associatedwith an electronic prepaid card or account such as redemption, valueaddition (e.g., topping up), activation, closure, fraud detection, etc.Specifically, the third party administrator can quickly and cheaplyadminister the transaction, including but not limited to determiningand/or providing the proper formatting for the sub-transaction, andfurther execute the sub-transaction independently and/or in cooperationwith the primary electronic wallet host or provider. Such formatting mayrelate to the particulars of information/data contained upon orassociated with a given value token (e.g., type of card number, securitycode, etc.) and/or the formatting of information or data associated witha particular transaction (e.g., the characteristics, organization,packaging, etc. of data such as card type, transaction type, securitycode, etc. into messaging fields or other data formats forreceipt/transmission while processing a transaction). For example, thethird party administration can pass the proper transaction formattingtemplate to the primary wallet provider. In at least one embodiment, thethird party administrator determines from the request, or requests fromthe user, the identity of the retailer associated with the transaction.Preferably, the third party administrator maintains a database of aplurality of transaction formats associated with a plurality ofretailers. After determining the identity of the retailer associatedwith the transaction, the third party administrator identifies theassociated transaction format for the identified retailer using theformat database and all subsequent processing is performed using theretailer-specific transaction format and vocabulary. In an embodiment, auser may wish to add a value token to an electronic wallet using aphysical stored value card. The user is requested to identify theretailer associated with the stored value card, for example via a userinterface located at a point of sale (including, in an embodiment, apoint of sale associated with a personal computer such as on-lineshopping via websites). In another embodiment, the user providesinformation associated with the stored value token via a web-based orpersonal digital assistant interface (e.g., a mobile phone app).Accordingly, based upon the user provided data, the appropriate formatmay be referenced from the database and the user may be shown apictorial representation or other mockup representation of the physicalstored value card with the specific input information highlighted on themockup. As such, the user knows exactly which inputs are required to addthe electronic value token to the electronic wallet. The user inputtedinformation derived from the mockup will be in the proper format and/ormay be further modified, packaged, etc. by the third party administratorto meet further formatting requirements. While the example described issimple, more complex transactions are also possible. As will bedescribed more fully herein, transactions relating to (i) using valuetokens in primary and/or sub-wallets for portions of transactions issimilarly handled as is (ii) exchanging value tokens in primary and/orsub-wallets for other types of value tokens or value tokens associatedwith other retailers. For example, a user may wish to exchange a valuetoken associated with a retailer the user does not frequent for a valuetoken associated with a retailer that the user does frequent. Moreover,the third party administrator may use the transaction format associatedwith the identified retailer for financial reconciliation of thetransaction or sub-transaction (e.g., debiting and crediting a prepaidaccount). In this instance, use of the proper transaction format is notonly convenient but often required.

As indicated above, an electronic sub-wallet is a specifically definedportion of an e-wallet located in or associated with a specific e-wallet(e.g., a primary or principal wallet). A sub-wallet may beadministered/maintained by the primary or principal e-wallet'sadministrator, processor, and/or provider or may be administered byanother party, system, processor, subroutine, or server. The separateadministration of the electronic sub-wallet allows the primary e-walletprovider and user to take advantage of economies of scale. For example,all electronic value tokens may be stored in one sub-wallet while creditand debit cards are stored in the primary e-wallet or a separateelectronic sub-wallet. As such, the provider of the primary e-wallet mayadministrate/perform transactions concerning value tokens associatedwith credit and debit cards residing in the primary e-wallet whileallowing a third party to administrate/perform transactions concerningvalue tokens associated with electronic value tokens residing in anelectronic sub-wallet, freeing the third party from costly banking andcredit regulations. Moreover, the third party administrator may use theeconomies of scale to receive payment for its services via arbitrage,commission, pay per transaction, or the like.

Via the separate administration of a sub-wallet, the third partyadministrator (e.g., administrator of an electronic sub-walletassociated with electronic prepaid accounts) provides convenience toboth the user and the primary electronic wallet provider. Often, thethird party administrator is the only entity with the knowledge andexpertise (e.g., a database of required transaction formats) to processfinancial reconciliations or other transactions associated with anelectronic prepaid account associated with a given issuer. For example,a third party administrator may be the only entity capable of matching aparticular transaction on the retailer's book to a particular use of avalue token or electronic wallet. As discussed in more detail herein, insome embodiments, the third party administrator carries out, implements,and/or is responsible for all or a portion of the functionalitydescribed in conjunction with the electronic value token transactioncomputer 150, for example in the context of administering one or moreelectronic sub-wallets (e.g., an electronic sub-wallet associated withelectronic prepaid accounts such as closed loop accounts issued onbehalf of one or more merchants) for the primary host or provider of anelectronic wallet such as a branded electronic wallet.

Access to the electronic wallet may be gated or protected by anauthentication token or other means for securely accessing an electronicwallet, examples of which include a proxy card or a personal digitalassistant or mobile device such as a smart phone. Other embodiments foraccess to the electronic wallet include cardless access such as anumber/password combination, a number without a password, and the like.Biometric information may also be used for authentication and accesspurposes, e.g. a fingerprint or iris print. Near field communicationtechnology may also be used to implement authentication tokens. Nearfield communication technology may be implemented at a physical point ofsale or in association with an online transaction. In either context,the near field communication technology may be implemented by a user viaa proxy card (e.g., 200, 201, or 203), personal computer, personaldigital assistant, smart phone 204, or other online transaction-relateddevice. Thus, the authentication token may be tangible, intangible, or acombination thereof. In an embodiment, the authentication token may begenerated, created, and/or formed at the initiation of an electronictransaction to uniquely identify the electronic transaction. In anembodiment, the uniquely generated authentication token may compriseelements of an electronic wallet identifier, a merchant identifier, apoint of sale identifier, an electronic value token identifier, anelectronic value token issuer identifier, an electronic value tokentransaction processor identifier, or combinations thereof. In anotherembodiment, the uniquely generated authentication token may be whollyunique and not comprise any portion of any previous identifier.

Examples of proxy cards are depicted in FIGS. 6A, 6B, and 6C. FIG. 6Adepicts a proxy card 200 in which the authentication information 211 isencoded on the card 200 by means of a bar code capable of being read byan optical scanner. FIG. 6B depicts a proxy card 201 in which theauthentication information 211 is encoded on a magnetic strip located onthe card 201. FIG. 6B depicts a proxy card 203 in which theauthentication information 211 is encoded on a near field communicationchip on the card 201. In some embodiments, the proxy card may have amagnetic strip and a bar code (or a plurality of magnetic strips and/orbar codes), and one or more of such may contain the authenticationinformation 211. The proxy cards 200, 201, and 203 are fabricated from asuitable first material, such as plastic, paper, a plastic-coated paper,laminates, or combinations thereof. The proxy cards 200, 201, and 203are typically made in a thickness range of from about 0.005 to about0.040 inch. The proxy cards 200, 201, and 203 each bear authenticationinformation 211, for example an account number, serial number,authorization code, digital signature, electronic key or key code, RFIDchip/data, etc. corresponding to an e-wallet. The proxy cardauthentication information 211 is unique to the proxy card andassociates the proxy card to an electronic wallet, and in an embodimentsuch association is stored in a database accessible by an administratorof the e-wallet. The authentication information 211 may be encoded in abar code as depicted in FIG. 6A on proxy card 200, a magnetic strip asdepicted in FIG. 6B on proxy card 201, a near field communication chipas depicted in FIG. 6C on proxy card 203, a series of numerals, a seriesof letters, or a combination thereof. The proxy cards 200, 201, and 203may also be fashioned with personal identification numbers, or PINs, tobe entered during the course of the transaction, that correspond to theauthentication information 211 and allows access and/or use of theelectronic wallet. In an embodiment, the PIN may be encoded in a barcode, a magnetic strip, a series of numeral, a series of letters, or acombination thereof. In an embodiment, the PIN may be obscured from viewby packaging, by an obscuring material such as a scratch-off strip orpeel-off label, or combinations thereof. In some embodiments, the proxycard may comprise a card security code (CSC), a card verification value(CVV or CV2), a card verification value code (CVVC), card verificationcode (CVC), verification code (V-code or V code), card code verification(CCV), credit card ID (CCID), or combinations thereof, and such codes(along with any other authentication data or token described herein) maybe employed in an authorization or authentication transaction, forexample initiated at a point of sale in conjunction with an e-walletpayment for a purchase transaction.

FIG. 6B depicts a proxy card 201 in which the authentication information211 is encoded on a magnetic strip located on the card 201. The magneticstrip may be made conventional construction, such as one deposited froma slurry, positioned on the card 201 so that it can be scanned inmagnetic strip reading equipment such as a Tranz terminal made byVerifone. For additional security, the authentication information 211may also be subjected to an encryption algorithm prior to encoding onthe magnetic strip.

In at least one embodiment, the proxy card 200 comprises a bar code,such as a UPC code (e.g., a GS1-128 or UCC/EAN-128), positioned on theproxy card 201 so that it can be scanned by well-known bar code readingequipment. Encoded in the bar code on the proxy card is a representationof the authentication information 211.

In other embodiments, series of numerals, series of letters, orcombinations thereof, may be placed on the proxy cards 200 and 201 to beread or interpreted by a human or a device, i.e. optical characterrecognition device, configured to interpret a series of shapescorresponding to the package identifier. Any suitable authenticationtoken as described herein such as virtual or cardless authenticationtokens, mobile phones, etc. may be employed in the various embodimentsdescribed herein.

In further embodiments, e.g., proxy card 203, near field communicationtechnology, radio frequency identification (RFID) tags, microprocessors,and/or microchips may be placed on the proxy card to be interpreted byspecifically configured devices. The RFID tags, microprocessors, and/ormicrochips may be used in addition to or in place of the bar code 255 onproxy card 200 and magnetic strip 256 on proxy card 201, or may be usedin combination with these or other means of encoding the authenticationinformation on the proxy card. Alternatively, such RFID or other meanssuch as near field, Bluetooth, etc. may be employed by a user operateddevice (e.g., a personal digital assistant such as a smart phone) toprovide electronic wallet access and/or authorization functionality. Inan embodiment, the authentication token is associated with a personaldigital assistant such as a smart phone 204, as depicted in FIG. 6D. Forexample, an electronic wallet stored in and/or accessed via a phone mayinclude an authentication token, or the phone itself may containhardware and/or unique electronic data (e.g., authentication data suchas serial number, MAC address, SIM card, digital signature, electronickey, user ID, phone number, passcode, etc.) that serves as theauthentication token. Such a phone may use near field communication tocommunicate data associated with the authentication token with a pointof sale device for authentication and transaction purposes. For example,the phone may be passed near the point of sale device and transfer userand/or wallet information and authentication information to the point ofsale device using near field communication protocol. The phone maytransfer all or a portion of the wallet and/or authenticationinformation, leaving the point of sale device to determine whichportions are applicable to the current transaction, or the phone maytransfer only presently applicable portions of information, i.e.information to be used during the current transaction, to the point ofsale device. That is, logic as to the transfer of wallet and/orauthentication information to/from the authentication token (e.g.,phone) and the point of sale device may reside on the authenticationdevice, on the point of sale device, or both. In an embodiment, thephone may provide hardware and/or software for authenticating a user,for example a camera or scanner and associated application forconfirming biometric data associated with the user, and uponauthenticating the user, the phone would convey the successfulauthentication to the point of sale device. The point of sale device maycommunicate with the wallet host or provider (e.g., a primary e-wallethost) and any sub-wallet hosts or providers, e.g., third partyadministrators. In another example, the point of sale device maycommunicate with only the wallet host or provider (e.g., a primarye-wallet host), and the wallet host or provider may communicate withthird party administrators, for example a sub-wallet host oradministrator. Despite multiple configurations to enable communication,the transaction may still occur in real time with no delay to thecustomer because the parties use scalable architecture.

In an embodiment, the authentication device is a proxy card. Although aproxy card is not a physical card, the proxy card's similar appearanceto a credit card, debit card, and/or stored-value card will helpadoption of and access to electronic wallets because consumers know howto use electronic value tokens. As such, consumers may come to think ofproxy cards as multiple cards rolled into one or simply think of a proxycard as an electronic wallet itself, despite being a physicalrepresentation. Authentication tokens may take and/or be associated withtangible or intangible embodiments such as a mobile device, a personalidentification number, a phone number plus a personal identificationnumber, a password, a username plus password, biometric identifier, andthe like. Authentication tokens contain, provide and/or are associatedwith authentication information (e.g., electronic authentication data orinformation), which associates a user with an electronic wallet. Assuch, multiple value tokens contained in the electronic wallet (or asub-wallet thereof) are associated with the user.

Returning to FIG. 4A, an electronic value token transaction computer 150accesses electronic wallets 10 from datastore 180. The prepaid or storedvalue card electronic value tokens may include electronicrepresentations of gift cards, loyalty cards, promotions, and the like.The POS device 111 obtains authentication information from an e-walletuser via an authentication token such as a smart phone or the proxy card200 and sends the authentication information (and is some instances,rules for allocating the contents of the e-wallet for the requestedtransaction) to the electronic value token transaction computer 150along with purchase information and/or value token information as partof a transaction request. The electronic value token transactioncomputer 150 uses the authentication information to locate the correctelectronic wallet 10 or sub-wallet in the datastore 180 and acts uponthe electronic value token (e.g., adds a value token to a primary walletor sub-wallet, activates a value token, debits a value token, tops-off avalue token, checks the balance of a value token, etc.) or examinesrules (received with the request, associated with the e-wallet by theelectronic value token transaction processing system 100, 1100, 1200, ora combination thereof) in light of the request's information. Forexample, for a purchase transaction the electronic value tokentransaction computer 150 selects the electronic value tokens that coverthe purchase based on the rules, for example rules associated with theorder or priority in which to apply or redeem value tokens to cover thepurchase price.

As shown in FIGS. 5A and 5B, the electronic value token transactioncomputer 150 comprises a rules unit 159. The rules unit 159 providesprocessing, management, associating, and implementing functionalitiesfor e-wallet (and sub-wallet) rules as provided, selected, and/orrequired by e-wallet users, e-wallet providers, e-wallet acceptingmerchants, electronic value token issuers, e-wallet transaction systemadministrators, and combinations thereof. The rules unit 159 mayfunction to associate provided, selected, and/or required rules withe-wallets and sub-wallets maintained in the database 180 and/or e-walletunit 199. The rules unit 159 may comprise a rules engine for derivingrules to be applied to a transaction in the absence of (or in place of)any particular rule provided or selected by any other rule assigningentity. The rules unit 159 may provide for e-wallet/sub-wallet rulesdata to be populated via (i) e-wallet user input (e.g., via kiosk, smartphone, personal digital assistant, and internet accessible userinterface); e-wallet provider input; (iii) e-wallet systemadministrator's input; (iv) or any combination thereof. For example, ane-wallet user may, via kiosk 189 interfacing, provide the electronicvalue token transaction computer 150 with specific, customized rulesdetailing the manner in which electronic value tokens contained in thee-wallet should be prioritized for use in satisfying transactions.Alternatively, the same e-wallet user could simply select the types ofrules applicable to the e-wallet from a list of options provided by thekiosk's 189 display. In addition, there may be instances, e.g., in asavings context, wherein certain laws, regulations, and/or policiesrequire that an e-wallet be limited to a given number of selectedtransactions per period (e.g., transfers from a savings-dedicatede-wallet).

In an embodiment, the rules can be created and configured by the user asa flowchart for selection of value tokens based on purchase information.For example, a rule may comprise selection of a closed loop-related(Store X branded) value token for a Store X purchase of any amount, withany remaining purchase balance to result in selection of an openloop-related (Credit Card Y) value token to fund such remainder.Alternatively, the user may invoke a rule that prescribes that openloop-related electronic value tokens should not be used to satisfybalances for closed loop-related electronic value token purchase, butrather debit card-related electronic value tokens residing in thee-wallet should be utilized to satisfy the balance instead. As such, auser may access and apply multiple value tokens with the efficiency ofusing one authentication token (e.g., one proxy card or smart phone).For example, the user may use an electronic gift card, an electroniccoupon, and two electronic credit cards from an electronic wallet orsub-wallet all in the time it takes to use only one physical card suchas a prepaid, debit, or credit card. The user, the retailer, issuers,vendors, merchants, advertisers, and other parties benefit from the timesaved, the ready access to multiple sources of value (e.g., multipleaccounts associated with the various value tokens), promotionalopportunities, transaction tracking and data mining regarding customerpurchasing behavior, promotional and advertising efficacy,real-time/point of product selection or purchase promotionalopportunities, etc.

In another embodiment, the rules may be established by the e-walletsystem provider (e.g., a primary and/or secondary e-wallet provider orhost). The e-wallet system provider may establish a rule concerninge-wallet allocations when there is no user established rule available(or if under the terms of a user's e-wallet use agreement the system'srules take precedent in designated transaction activities). For example,the e-wallet system may put a rule in place that directs the electronicvalue token transaction computer 150 to first apply an e-wallet systemprovider's own branded electronic value token residing in the user'se-wallet to satisfy the requested transaction when the transactionconcerns, relates, or involves an affiliate and/or contractually-relatedentity of the e-wallet system provider. As such, this type of rule couldallow for the e-wallet system provider and its affiliates and/orcontractually-related entities to maximize revenues or other businessobjectives based on use of the e-wallet system and other synergisticeffects.

In a further embodiment, the e-wallet's rules may be fashioned toautomatically direct electronic value token exchange activities(electronic value token exchange will be discussed in more completedetail herein). For example, the e-wallet user may manage the e-wallet(as will be described in more detail herein, e.g., in relation to FIGS.9A-D) so that upon the occasion when the user presents the e-wallet tosatisfy a transaction at retail establishment, e.g., Retailer Q, and thee-wallet contains no Retailer Q branded electronic value tokens, thee-wallet will automatically, and in real time, initiates an electronicvalue token exchange process wherein the e-wallet communicates a requestfor electronic value token exchange to the electronic value tokentransaction computer 150. Additionally or alternatively, the user may bepresented in real-time with a promotion to obtain a retailer-specificvalue token (e.g., a real-time offer for a store branded value tokensuch as a credit account). In this example, the e-wallet user may mangethe e-wallet so that all electronic value tokens associated with prepaidservices (gift card-type electronic value tokens) are located in adesignated sub-wallet and each of said electronic value tokens may beplaced/ordered/designated in the sub-wallet via a preferential rankingsystem, e.g., most preferred electronic value token or token type (e.g.,#1) to least preferred electronic value token or token type (e.g., #22,if there are 22 types of electronic value tokens in the sub-wallet). Forexample, Retailer M branded electronic value tokens may be designated asmost preferred and Retailer L branded electronic value tokens may bedesignated as least preferred. Further in the example, the e-wallet alsohas been provided with rules by the user that directs the e-wallet, incircumstances wherein the e-wallet has been presented to facilitate atransaction at a retailer in which the e-wallet contains none of saidretailer's electronic value tokens (the e-wallet will recognize theretailer based on information exchanged between the e-wallet and theretailer's communication devices at the onset of the originaltransaction), such as the Retailer Q scenario described above, thee-wallet rules direct the e-wallet to initiate an electronic value tokenexchange request and to include in said request the exchange of theleast preferred electronic value token residing in the e-wallet, i.e.,the Retailer L branded electronic value token (#22) and if necessarypreferred electronic value token #21, #20, etc., for a Retailer Qelectronic value token in an amount sufficient to meet the originaltransaction's amount. The electronic value token transaction computer150, upon receipt of the electronic value token exchange request,communicates with an electronic value token exchange program 2000 (whichis part of the overall electronic value token transaction processingsystem 100, 1100, or 1200) to effectuate the requested electronic valuetoken exchange. The requested electronic value token exchange isperformed, the e-wallet receives the requested Retailer Q brandedelectronic value token, which is coincidentally used in conducting theoriginal transaction, and the e-wallet surrenders (or makes unavailablefor use and only available for modification) the Retailer L brandedelectronic value token to the electronic value token transactioncomputer 150, which in this case was actually valued in excess of therequested Retailer Q branded electronic value token. As such, theelectronic value token transaction computer 150, modifies the value ofthe Retailer L branded electronic value token (either internally or viacommunication with the Retailer L branded electronic value token'sissuing system) to reflect the value reduction based on the providedRetailer Q branded electronic value token, extracts the exchange ratefor the exchange of the Retailer Q branded electronic value token forthe Retailer L branded electronic value token (as will be discussed morefully herein), communicates the transactional information to allinterested parties, and returns (or makes available again) thevalue-modified Retailer L branded value token to the user's e-wallet. Inan alternate embodiment, the e-wallet's electronic value token exchangerules could have provided that the e-wallet query the electronic valuetoken transaction computer 150 regarding the best available exchangerate for the electronic value tokens residing in the e-wallet and makethe exchange based on the best exchange rate rather than the ranking ofthe electronic value tokens.

FIG. 5A illustrates an exemplary electronic value token transactionprocessing system 100 in accordance with one embodiment. As shown, theelectronic value token transaction processing system comprises: (a) atleast one point of sale device 111; (b) an electronic wallet processingsystem, e.g., electronic value token transaction computer 150; (c) adatastore 180 containing an electronic wallet unit 199 storingelectronic value tokens, e.g., 804, 827, 828, and 829, such as accountnumbers, electronic wallet account information, value added awardconditions (herein “value added award” is synonymous with “value addedbonus,” “value added bonus award,” “value added award bonus,” and “valuedifferentiation”), and other information related to adding, redeeming,and managing the electronic value tokens; (d) at least one individualissuers' authorization system 160; and (e) any other unit included inthe system by the electronic value token transaction computeradministrator 151. In one embodiment, the electronic value tokentransaction computer 150 comprises a value added determination unit 153,a point-of-sale (“POS”) interface 152, a message modification unit 154,a reconciliation unit 155, an issuer system interface 156, anauthorization unit 157, and a sorting unit 198. In an embodiment, theelectronic value token transaction computer 150 (or a unit thereof suchas sorting unit 189) further comprises token exchange interface, whichmay communicate with electronic value token exchange program 2000. ThePOS Interface 152 provides a means for the electronic value tokentransaction computer 150 to communicate with the point of sale device111 via, for example, the Internet, a Public Switched Telephone Network(“PSTN”), or an independent dedicated network. Likewise, the electronicvalue token transaction computer 150 may communicate via issuer systeminterface 156 with the issuers' authorization system 160 via, forexample, the Internet, a Public Switched Telephone Network (PSTN), or anindependent dedicated network. Communications 106, 107 between the POSinterface 152 and the point of sale device 111 and communications 109,110 between the issuer system interface 156 and the issuers'authorization systems 160 may be encrypted for added security and/or mayutilize a virtual private network (“VPN”). The sorting unit 198 may sortthe communications into various types for routing in various ways. Forexample, the sorting unit 198 may identify and sort electronic walletand/or sub-wallet requests (e.g., upon receipt of authorizationinformation with a transaction request, the sorting unit 198 can routethe requested transaction to a specific electronic wallet maintained bythe system and/or to a specific sub-wallet or sub-wallets associatedwith an electronic wallet), balance inquiry requests, registrationrequests, activation requests, redemption requests, and managementrequests for routing to the various units of FIG. 5A. The electronicvalue token transaction computer 150 or sorting unit 198 may alsogenerate messages based on the requests for similar routing.

As can be seen in FIG. 5A, at the point of sale device 111 (typicallylocated at a vendor and/or redeeming merchant or retailer, butalternatively located at a kiosk 189 or at a user's home or office wherea personal computer is configured to act as a point of sale, for exampleduring an on-line transaction), the authentication token is interpretedby a point of sale interpretation unit 101 (e.g., a card reader). Thepoint of sale interpretation unit 101 can comprise a human, a bar codescanner, magnetic strip reader, optical character recognition device,biometric device, numerical keyboard (e.g., for entering a tokenidentification number) or other device configured to interrogate,interpret, capture, or input the data encoded in or on theauthentication token.

About contemporaneously with (or, alternatively, prior or subsequent to)the interpretation of the authentication token, a request for anelectronic wallet transaction by a point of sale transaction unit 104 ismade. The point of sale transaction unit 104 can comprise a human, anelectronic input device, a register or terminal, a computer processingunit (“CPU”), a personal computer, a personal digital assistant (e.g.,smart phone) or other means of requesting or messaging interpreted bythe point of sale interpretation unit 101 and/or point of saleprocessing unit 105. In some embodiments, the actions performed by thepoint of sale interpretation unit 101 and the point of sale transactionunit 104 may be performed by one unit capable of performing both actionsthat would be performed by the individual units, for example a point ofsale register/terminal or a personal computer during an on-line,web-based transaction.

The point of sale interpretation unit 101 and the point of saletransaction unit 104 communicate with the point of sale processing unit105. The point of sale processing unit 105 can comprise a CPU or othertype of processing device accepted for use in the industry. The point ofsale interpretation unit 101 communicates authentication information 102to the point of sale processing unit 105. The point of sale transactionunit 104 communicates the request 103 for an electronic wallettransaction to the point of sale processing unit 105. The point of saleprocessing unit 105 may combine this information to communicate with theelectronic value token transaction computer 150 (e.g., transmits amessage requesting an electronic wallet transaction along with theassociated transaction and/or authentication data). In an embodiment,the point of sale processing unit 105 stores and/or receives from theelectronic value token transaction computer 150 (or a sub-administratoror unit associated therewith, such as a sub-wallet administrator) atransaction format associated with the POS retailer and/or associatedwith a given transaction type and/or value token, and such transactionformat may be used to format the transaction request or message, toprompt the user for further information, or for other data gathering ortransmit/receive features at the point of sale. For example, a usermaking a purchase at a retailer operates a card reader. A card readermay a display with an input device and a barcode reader or magneticstrip scanner. The card reader may be touch sensitive and may havevarious buttons used for input. Following the card reader prompts, theuser sees the options “Debit,” “Credit,” and “E-Wallet.” The userselects “E-Wallet.” The user then sees the options “Purchase,” “AddToken,” and “Delete Token.” The user selects “Purchase.” Followingadditional prompts (which in an embodiment relate to a transactionformat specific to the particular retailer of the point of sale), theuser enters a PIN number. In some embodiments, the actions performed bythe point of sale interpretation unit 101, the point of sale transactionunit 104, and the point of sale processing unit 105 may all be performedby one unit (e.g., an integrated POS device such as a computerizedregister) capable of performing all the actions that would be performedby the individual units.

The point of sale processing unit 105 is connectable to the electronicvalue token transaction computer 150 via a suitable network, such as theInternet, the public switched telephone network (PSTN), or anindependent dedicated network. Each point of sale processing unit 105has an associated identifier (e.g., a terminal identifier or serialnumber) that may be transmitted to the electronic value tokentransaction computer 150 during the course of connecting the point ofsale processing unit 105 to the electronic value token transactioncomputer 150. Each point of sale processing unit 105 may includemultiple point of sale transaction units corresponding to individualterminals each with its own terminal identification, for example presentwithin a given store location.

As depicted in FIG. 5A, the electronic value token transaction computer150 is configured to: (a) form a secure connection with theretailer/merchant and/or vendor (e.g., via the point of sale device 111,customer internet access, or kiosk 189), the issuers' authorizationsystems 160, and any other entities 190 authorized to access theelectronic value token transaction computer 150 by the electronic valuetoken transaction computer administrator 151; (b) to communicate withissuers' authorization systems 160 to request and receive redemption oraddition of value tokens into electronic wallets; (c) to communicatewith issuers' authorization systems 160 to redeem all or a portion ofthe electronic value tokens associated with the electronic wallet; (d)generate and maintain a transaction log 170 of all activities performed;(e) generate and maintain an error log 175 of all activitiesunsuccessfully completed and reasons therefore; (f) communicate to theretailer/merchant and/or vendor (e.g., via the POS unit 111) theredemption or addition of value tokens into electronic wallets and anyinformation concomitant with the redemption or addition of value tokensinto electronic wallets; and (g) communicate to the retailer/merchantand/or vendor (e.g., via the POS unit 111) any reasons why transactionscannot not be completed.

The electronic value token transaction computer 150 may comprise asingular processing unit (e.g., a centralized server), a plurality ofprocessing units (e.g., a distributed computing system with variousunits distributed and in communication with each other), or combinationsthereof, with concomitant storage capabilities, each capable of ordesignated for: accessing the datastore 180; creating a transaction log170; creating and maintaining an error log 175; communicating withretailers/merchants and/or vendors, e.g., at a point of sale, includingvia the internet for on-line transactions; communicating with theindividual issuers' authorization systems 160; processing individualvalue token and electronic wallet requests; processing redemptionrequests; processing value added functions to add additional cash valueor add an electronic redemption coupon for a specific product(s) orservice(s); processing redemption request for electronic redemptioncoupons for specific product(s) and/or service(s); and communicatingwith other systems 190 capable of and authorized to communicate with theelectronic value token transaction computer 150.

Datastore 180 maintains records of accounts associated with eachelectronic wallet indicating: (a) whether each individual value tokenhas been added or redeemed, (b) whether the authentication token hasbeen registered, (c) records and details of each individual redemptionrequest, (d) the amount remaining on the electronic value tokens, (e)rules required for redeeming the electronic value tokens, (f) identityof the issuers of the electronic value tokens, (f) value added bonusawards, (g) rules for redeeming value added bonus awards, and (h) anycombination thereof. The datastore may also maintain records of rulesrequired for granting a value added bonus award to an electronic walletor value token.

Datastore 180 also maintains records associated with each electronicwallet and/or sub-wallet indicating: (a) timing of, and otherinformation related to, registration activities; (b) timing of, andother information related to, management activities; (c) timing of, andother information related to, transaction activities; (e) rulesapplicable; (f) identity of the issuers electronic value tokens therein;(f) identity of sub-wallets associated therewith; (h) any other recordsrequested by issuers, merchants, vendors, advertisers, users, or otherinterested parties; and (i) any combination thereof. While a singledatastore 180 is shown, it should be understood that a plurality ofdatastores may be employed, and relevant data divided among thedatastores in any suitable manner to meet the various processes andobjectives described herein. Also, the various data may be associatedwith one or more datastores closely coupled to and/or located inproximity to one or more sub-units, sub-processors, third partyprocessors, and the like associated with the electronic value tokentransaction computer 150, and such datastores preferably have data usedby such sub-units, sub-processors, and third party processors.

The electronic value token transaction computer 150 is also configuredto generate and maintain a transaction log 170 of all activity involvingthe electronic value token transaction computer 150. The transaction logmay comprise a detailed summary of transaction types such as: (a)requested value token additions; (b) requested value token sales; (c)requested value token redemptions; (d) requested value token exchanges;(e) the monetary amount ascribed to value token additions; (f) themonetary amount ascribed to value token redemptions; (g) the monetaryvalue ascribed to value token exchanges; (h) the value added amounts,products, or services additions; (i) the value added amounts, products,or services redemptions; (j) the time the electronic value tokens wereadded; (k) the time the electronic value tokens were redeemed; (l) thetransaction or communication performed with the issuer for adding valuetokens; (m) the transaction or communication performed with the issuerfor redeeming value tokens; (n) the PIN communicated to the vendor inresponse to a request to add a value token requiring the input of a PINfor use; (o) e-wallet registration; (p) e-wallet set-up activities; (q)e-wallet transaction activities; (r) e-wallet savings activities; (s)e-wallet management activities; (t) any other information the electronicvalue token transaction computer administrator 151 directs theelectronic value token transaction computer 150 to maintain as a logentry; and (u) any combination thereof.

The information contained in the transaction log 170 may be used fordata mining purposes, e.g., to generate reconciliation reports,settlement reports, payment reports, audit reports, e-walletregistration reports, e-wallet management reports, e-wallet usagereports, e-wallet savings reports, electronic value token purchasereports, electronic value token redemption reports, electronic valuetoken exchange reports, electronic value token sale reports, or otherforms of information aggregation for the benefit of, use by, or forprovision to, the electronic value token transaction administrator 151,the datastore administrator 181, vendors, issuers, issuers'authorization systems 160, redeeming merchants, or other interestedparties. For example, the transaction log 170 contains information abouteach transaction performed by electronic value token transactioncomputer 150 (and any sub-components thereof) and may be utilized by thereconciliation unit 155 when reconciling accounts belonging to variousvendors, merchants, issuers and the electronic value token transactionprocessing system administrator(s). Additional data miningconsiderations that may be recorded, analyzed, and/or providedinterested parties (e.g., vendors, merchants, issuers, advertisers,etc.) include data about: (i) the purchase habits of e-wallet users;(ii) electronic value token purchases, sales, redemptions, andexchanges; (iii), special offer and/or value added activities; (iv)loyalty-related activities; and (v) savings-related activities, all ofwhich can be used for marketing, inventory, and other purposes.

Oversight and maintenance of the electronic value token transactioncomputer is performed by the electronic value token transaction computeradministrator 151. Although not required, in an alternative embodiment,the electronic value token transaction computer administrator 151 mayalso function as the datastore administrator 181. The electronic valuetoken transaction computer 150 is configured to generate and maintain anerror log of all transactions that were not completed and reasonstherefore. In some embodiments, the error log is administered by theelectronic value token transaction computer administrator 151.

The electronic value token transaction computer 150 is also configuredto communicate with other entities 190 authorized to access theelectronic value token transaction processing system and specificallyauthorized to access the electronic value token transaction computer150. These other entities may comprise third party payment managementsystems, third party audit systems, issuer affiliated entities, vendoraffiliated entities, redeeming merchants or redeeming merchantaffiliated entities, financial institutions such as banks, credit cardagencies, or credit unions, or any other entity provided access by theelectronic value token transaction computer administrator 151 or otherentity having authority to grant access.

The transaction request from the point of sale device 111, or otheraccess point, associated with an e-wallet may contain one or more of thefollowing pieces of information: (a) authentication information, (b)point of sale terminal identification, (c) amount to be credited ordebited, (d) the time of the request, (e) the date of the request, (f)identification of the issuer, (g) identification of the vendor, (h)location of vendor, (i) identification of the product(s) and/orservice(s) being purchased, (j) an activation or deactivation request,(k) a wallet management function such as addition of a value token,deletion of a value token, exchange of a value token, changingmanagement or processing rules associated with one or more value tokens,partitioning a wallet into sub-wallets or vice-versa, etc., (l) and anycombination thereof. However, the information contained within therequest is not limited to the enumerated list but may comprise otheritems in addition to the items enumerated or in place of the itemsenumerated above.

Upon receipt of the electronic wallet transaction request from the pointof sale, and identification and sorting as such by the sorting unit 198,the electronic value token transaction computer 150 accesses theelectronic wallet unit of datastore 180. The electronic value tokentransaction computer 150 processes the information contained in thedatastore 180 and communicates 109, 110 with the individual issuers'authorization systems 160 to effectuate management of the electronicvalue tokens and corresponding accounts. The message modification unitmay adjust the messages and requests so that multiple units,sub-components/processors, or third-party administrators can recognizeand correctly interpret the messages. For example, after the electronicvalue token transaction computer 150 determines the individual issuers'authorization systems 160 associated with the request, the messagemodification unit 154 accesses the database 180 to determine theappropriate transaction messaging formats for each individual issuers'authorization systems 160 and then formats the subsequent communicationsto said individual issuers' authorization systems 160 using theindividual issuers' authorization systems 160 specified/preferredtransaction format and vocabulary. The electronic value tokentransaction computer's 150 communication with the individual issuers'authorization systems 160 may occur simultaneously or independently. Theelectronic value token transaction computer 150 is connectable to theindividual issuers' authorization systems as via a suitable network,such as the PSTN, the Internet, or an independent dedicated network. Theelectronic value token transaction computer 150 is configured to sendand/or receive communication 110 from the issuers' authorization systems160 concerning the status of the electronic value tokens.

The reconciliation unit 155 reconciles the accounts of various issuers,selling vendors, and/or redeeming merchants, to credit and debitappropriate merchants, vendors, the electronic value token transactionprocessing system administrator, and issuers with the value of varioustransactions to reflect which entities received value from which otherentities. For example, if a vendor A sells a value token issued byissuer B for a specified amount and receives payment from a user whoadds the electronic value token to the user's electronic wallet, theselling vendor receives a percentage (e.g., retains a percentage) of thepurchase amount and/or a predetermined amount, the electronic valuetoken system administrator receives a percentage of the purchase amountand/or predetermined amount for processing the transaction, and theissuer receives the remainder. If a value token issued by issuer Y isredeemed at merchant X to purchase items, then the amount redeemed isdebited to the issuer Y and credited to the merchant X, sometimes minusa transaction fee collected by the issuer and/or a transaction orprocessing fee collected by the electronic value token transactionprocessing system administrator.

Authorization unit 157 is utilized when the electronic value tokentransaction computer 150 is also the authorizing system such that theelectronic value token transaction computer 150 authorizes electronicwallet requests rather than transmitting the request to the issuers'authorization systems 160 for authorization. The authorization unit 157may perform the same and/or different functions as described forauthorization systems 160 and vice-versa.

The authorization unit 157 will validate the formatting of the e-wallettransaction request (e.g., primary or sub-wallet) received from the POSprocessor 105 (or other transaction originatingdevice/component/processor). In other words, the authorization unit 157will check the data fields in the request to confirm that the fields arepopulated with data and that the data is in the correct format (e.g.,length, alphanumeric format). If the request is improperly formatted,the authorization unit 157 will reject the request, or in someembodiments may retrieve the proper format (e.g., from a formatdatabase) and modify the transaction request to comply with the properformat. The authorization unit 157 also performs various validationchecks on the request. The authorization unit 157 verifies card-relatedtransaction information based on an analysis of several criteria, suchas: 1) determining that the UPC code for the product is present in thedatastore 180 (or other database such as an issuer's database) for theelectronic value token transaction processing system 100; 2) determiningthat the value amount of the requested transaction corresponds to thecustomer's payment for the subject transaction request, e.g., whetherthe UPC information identifies the card as a $25.00 card and that thecorresponding transaction request includes a $25.00 payment by thecustomer; 3) determining that the UPC information identifies the card asbeing a type of card available for processing by the requestingmerchant; and 4) determining that the Bank Identification Number (“BIN”)of the card (i.e., the first six digits of the card's identificationnumber), which identifies the card issuer, corresponds to the UPCinformation identifying the card issuer.

The authorization unit 157 may also verify transactions based on othercriteria such as transaction velocity (number/amount per unit time). Forexample, if a card processor is concerned that multiple voidtransactions are indicative of fraudulent activity, the card processorcould ask that the electronic value token transaction processing system100 monitor the number of void transactions requested and rejecttransactions from terminals that exceed a pre-selected amount of voidtransactions per unit time. Lastly, the authorization unit 157 may beconfigured to reject transaction requests in the event that theinformation received by the authorization unit 157 is unintelligible.

If the request is properly formatted and is validated as describedabove, the electronic value token transaction computer 150 may transmitdetails of transactions to the issuers' authorization systems ratherthan authorization requests. Also, in some embodiments, the issuer, theauthorizing system (e.g., authorization unit 157), and the transactioncomputer are part of the same entity and, in such an embodiment, therewould be no issuers' authorization systems 160 or the issuers'authorization systems 160 would be under common control with the otherunits of the electronic value token transaction computer 150 (forexample, a commonly owned and operated computing system, that may becentralized (e.g., part of a centralized data center) and/or distributedwithin a commonly owned or controlled system or network). Furthermore,it should be noted that although units associated with the electronicvalue token transaction computer 150 (e.g., units 152-157) are depictedas various units within a single data processing system for illustrationand conceptual purposes, one or more of units 152-157 could beimplemented on separate computers, systems, or servers in a distributeddata processing environment.

An exemplary process utilized by an electronic value token transactioncomputer 150 for facilitating a purchase using an electronic wallet inaccordance with a primary e-wallet transaction processing embodiment isdepicted in FIG. 7A. Such an embodiment may be exemplified by thee-wallet transaction processing request being both initially received byand subsequently performed by the electronic value token transactionprocessing system 100. The actions depicted can be performed in theorder shown or in a different order, and two or more of the actions canbe performed in parallel.

In block 302, the electronic value token transaction computer 150receives a request or multiple requests from a point of sale terminal.In at least one embodiment the requests may comprise an electronicwallet transaction request, a balance inquiry request, a registrationrequest, an activation request, or a redemption request, a walletmanagement request, and contains one or more of the following: (a)identity of the terminal, (b) authentication information, (c) the amountof the purchase, (d) the identity of the electronic value token issuer,(e) the identity of the vendor, (f) the identity of the location, (g)the time of the request, (h) the date of the request, (i) informationexpressly identifying the request as an e-wallet transaction request(e.g., transaction type data); (j) information identifying a primarye-wallet, sub-wallet(s), or a combination thereof; (k) any othertransaction and/or authentication data described herein; and (l) anycombination thereof. The request at block 302 may comprise otherinformation, requests or functions, for example of the types describedherein, in addition to or in place of the above enumerated items. In atleast one embodiment, the authentication information is based on anauthentication token selected from the group consisting of proxy cardand cellular phone. Using the identity of the electronic value tokenissuer, transactions may be correctly formatted for communication withthe electronic value token issuer.

Using information contained within the electronic wallet transactionreceived from the point of sale device 111 and/or from informationobtained from datastore 180, in block 304, the electronic value tokentransaction computer 150 determines whether the request is an electronicwallet request containing valid authentication information and whetherthe request is for redemption of a value token(s), addition of a valuetoken(s), deletion of a value token(s), or management of the electronicwallet. The electronic wallet request may comprise a bank identificationnumber (“BIN”) located on the proxy card as part of the authenticationinformation. The sorting unit may decode the BIN number or otherwiseverify that the request is an electronic wallet request.

Using information contained within the electronic wallet transactionreceived from the point of sale device 111 and/or from informationobtained from datastore 180, in block 324, the electronic value tokentransaction computer 150 identifies/determines the primary e-wallet,sub-wallet(s), and/or locations of said e-wallet or sub-wallet(s)indicated/necessary to effectuate the received e-wallet transactionrequest. If the authorization information received indicates therequested e-wallet transaction involves a primary e-wallet, sub-wallet,or combinations thereof maintained by the electronic value tokentransaction computer 150, the electronic value token transactioncomputer 150 may (i) apply its own logic to the request; (ii) applyrules stored in a primary wallet (e.g., rules established by theelectronic value token transaction processing system administrator, theprimary e-wallet user, or a combination thereof); (iii) apply rulesstored in a sub-wallet (e.g., rules established by the electronic valuetoken transaction processing system administrator, the sub-wallet user,or a combination thereof) (iv) apply rules received with the requestfrom the point of sale 111 (e.g., contemporaneous rules submitted withthe request by the user of the primary e-wallet/sub-wallet); (v) or anycombination thereof.

For example, an embodiment may include the electronic value tokentransaction computer 150 determining that the entire request is relatedto value tokens contained in a primary e-wallet. Upon receipt of therequest, the electronic value token transaction computer 150 will queryits authorization unit 157 (as described more fully herein), itsdatastore 180, the E-Wallet unit 199, and any other necessary unit todetermine whether the primary e-wallet comprises value tokens capable ofmeeting the subject request (e.g., whether the primary e-wallet containsvalue tokens associated with vendors, merchants, and/or issuers relatedto the requested transaction). Such determination may be performed bycomparing electronic value token identifications, user IDs, requestedtransaction types. The electronic value token transaction computer 150will subsequently evaluate the manner in which the electronic valuetokens available in the primary e-wallet corresponding to the requestwill be applied under the primary e-wallet's rules and/or rules receivedwith the request, and perform or refuse to perform the requestedtransaction and/or transactions.

Another embodiment may include the electronic value token transactioncomputer 150 determining that the entire request is related to valuetokens contained in a sub-wallet. Upon receipt of the request, theelectronic value token transaction computer 150 will query itsauthorization unit 157 (as described more fully herein), its datastore180, the E-Wallet unit 199, and any other necessary unit to determinewhether the sub-wallet comprises value tokens capable of meeting thesubject request (e.g., whether the sub-wallet contains value tokensassociated with vendors, merchants, and/or issuers related to therequested transaction). Such determination may be performed by comparingelectronic value token identifications, user IDs, requested transactiontypes. The electronic value token transaction computer 150 willsubsequently evaluate the manner in which the electronic value tokensavailable in the sub-wallet corresponding to the request will be appliedunder the sub-wallet's rules and/or rules received with the request, andperform or refuse to perform the requested transaction and/ortransactions.

In another example, an embodiment may include the electronic value tokentransaction computer 150 determining that a portion of the entiretransaction request is related to electronic value tokens residing in aprimary e-wallet while a portion of the transaction request is relatedto electronic value tokens residing in a sub-wallet(s). Suchdetermination may be made by evaluating the requested transaction type,the electronic value token identification, or any other methods fordetermining transaction allocation. The electronic value tokentransaction computer 150 will evaluate the manner in which theelectronic value tokens available in the primary e-wallet correspondingto the request will be applied under the primary e-wallet's rules (asthose rule may affect payment methods to be employed which are locatedin the primary e-wallet), the electronic value token transactioncomputer 150 will evaluate the manner in which the electronic valuetokens available in any applicable sub-wallet corresponding to therequest will be applied under such sub-wallet's rules and/or rulesreceived with the request, and perform or refuse to perform therequested transaction and/or transactions.

In an exemplary embodiment, at block 324, the electronic value tokentransaction computer 150 may identify, in response to a receivedtransaction request, one or more value tokens in a primary e-wallet andone or more electronic value tokens in a sub-wallet that, when usedtogether, will cover the entirety of the requested e-wallet transaction.Moreover, one of the electronic value tokens located in the primarye-wallet or sub-wallet may be an electronic representation of a loyaltycard and another electronic value token located in either the same ordifferent location of said loyalty card value token may be an electronicrepresentation of a retailer's gift card. In such an example, theelectronic value token transaction computer 150 can effectuate thecoincidental use of the “loyalty card” token and the “retailer's giftcard” token, regardless of the tokens' locations in the primary e-walletand/or sub-wallet(s) to allow for an enhanced user benefit as opposed tonot coincidentally applying the value of the “retailer's gift card”token and the “loyalty card” token for the transaction, e.g., a 5%increase in the value of the “retailer's gift card” token or loyaltypoint bonus applied to the “loyalty card” token for the use of the“retailer's gift card” token.

A value token may be associated with a closed loop account or open loopaccount. A closed loop account typically expires after the funds in theaccount have been depleted, e.g. a gift card account. An open loopaccount does not typically expire. Rather, there is typically an ongoingobligation for various entities to credit and debit the account, e.g. abranded credit card account or debit card account such as Visa orMastercard. Closed loop accounts are often associated directly withretailers while open loop accounts are often associated with financialinstitutions (e.g., Chase or Citi issued Visa). In at least oneembodiment, the electronic value tokens comprise closed loop accountnumbers and open loop account numbers. The closed loop account numbersare associated with retailers able to debit or credit closed loopaccounts associated with the closed loop account number. The open loopaccount numbers are associated with financial institutions able to debitor credit open loop accounts associated with the open loop accountnumbers. The electronic value token may have an expiration date orspecified dates of use that are different from any other value tokens.Furthermore, the electronic value tokens may identify specificmerchants, locations, and/or products with which the electronic valuetokens may be utilized.

If the request is for value token addition, then in block 306, theelectronic wallet is created (if not already created) and the electronicvalue token is added to the electronic wallet. The following Tablesinclude elements, parameters, and information included in e-wallettransaction communications and used by the electronic value tokentransaction processing system 100 to facilitate and effectuate e-wallettransactions.

Table 1A illustrates request parameters requested to create a wallet inat least one embodiment. Table 1B illustrates response parametersrequested to create a wallet in at least one embodiment.

TABLE 1A Request Parameters Data Suggested Element Type LengthDescription accounttype String 200  Account Type loadamt decimal N/AAmount to be loaded into the wallet account loadamtcurrency string  3Denomination Type. txn-uniqueidentifier string 12 Unique transaction id.

TABLE 1B Response Parameters Element Data Type Description accountidstring Unique identifier for a account accounttype string Type of theaccount. currency string Denomination Type. balance decimal Balanceavailable in the account uniqueidentifier string The unique identifieridentifies a (numeric) transaction. code string The Status of therequested transaction. description string The Status description of therequested transaction.

The electronic value token transaction computer 150 preferably allocatesmemory for the electronic wallet and value token(s) and associates theaccount number with the electronic wallet and/or authenticationinformation stored in the electronic wallet unit 199 by storing thepieces of information in a data structure on the datastore 180. Table 2illustrates the parameters for a gift card value token in at least oneembodiment.

TABLE 2 Suggested Element and Description Data Type Lengthstatusinfo.status.code String 7 statusinfo.status.description String 500card.retailer.id Integer String 11 card.retailer.name String 100card.number String 50 card.securitycode String 50 card.expirydateInteger String 6 card.activationdate Date String 20 card.initialbalanceDecimal String 10 card.currentbalance Decimal String 10card.currentbalanceasof Date String 20 card.customerservice.phone String20 card.customerservice.website String 256 card.currency String 3

Table 3 illustrates more detailed parameters for a gift card electronicvalue token in an alternative embodiment, including the designation ofassociated wallet(s) and/or sub-wallet(s).

TABLE 3 Element and Suggested Description Data Type Lengthcard.retailer.id Integer String 11 card.retailer.name String 100card.number String 50 card.securitycode String 50 card.expirydateInteger String 6 card.registeredto String 10 card.activationdate DateString 20 card.initialbalance Decimal String 10card.islookedupinitialbalance String 1 card.currentbalance DecimalString 10 card.islookedupcurrentbalance String 1card.customerservice.phone String 20 card.customerservice.website String256 card.notes String 500 card.nickname String 100 card.currency String3 card.user.firstname String 50 card.user.lastname String 50card.user.address.line1 String 50 card.user.address.line2 String 50card.user.address.city String 50 card.user.address.state String 50card.user.address.zip String 5 card.user.phone.number String 10card.user.email.address String 128 card.additionalinfo1 String 300card.additionalinfo2 String 300 card.additionalinfo3 String 300wallet.id Integer String 10 Collection of folders wallet.folder.1.idInteger String 10 wallet.folder.1.name String 100 wallet.folder.2.idInteger String 10 wallet.folder.2.name String 100 [. . . More folders]

The request, however, may be modified for other reasons unrelated to theadd token decision and forwarded to the appropriate one of the issuers'authorization systems 160 as part of the reconciliation process, forexample the request could concern redemption, deletion, reloading value,added value, balance inquiry, or a combination thereof, each of whichwould be communicated to the issuers' authorization systems 160 forreconciliation.

Table 4 illustrates formatting for authentication communication.

TABLE 4 Element and Description Data Type client_ref_id String signatureString timestamp String(in the format yyMMddHHmmssSSSz) nonce Stringencryption_type String usertoken String uuid String user_ip Stringchannel String

Each request is authenticated using the signature, a user isauthenticated with username/password or open id, the session isvalidated using the user token. A client may send client_ref_id,timestamp, nonce, encryption_type, channel, user_ip, signature,optionally usertoken with each request to be able to validate eachmessage.

Table 5 illustrates the parameters used to retrieve a user's wallet.

TABLE 5 Element Data Type Description accountid string Unique identifierfor a account accounttype string Type of the account. currency stringDenomination Type. balance decimal Balance available in the account codestring The Status of the requested transaction. description string TheStatus description of the requested transaction.

Table 6A illustrates the request parameters used to redeem value from atoken in the wallet.

TABLE 6A Request Parameters Data Suggested Element Type LengthDescription accountid String 100  Unique identifier for the accountredamt decimal N/A Amount to redeem from the account redamtcurrencystring  3 Amount Type. txn-uniqueidentifier string 12 Unique transactionid. txn-istimeoutreversal bool N/A 0, if it is not a reversal of anytransaction type 1, if it is a reversal transaction.

Table 6B illustrates the response parameters used to redeem value from atoken in the wallet.

TABLE 6B Response Parameters Data Suggested Element Type LengthDescription accountid string 100 Unique identifier for a accountaccounttype string 50 Type of the account. currency string 3Denomination Type. balance decimal N/A Balance available in the accountuniqueidentifier string 12 Unique identifier for the transaction. codestring 7 The Status of the requested transaction. description string 500The Status description of the requested transaction.

Table 7A illustrates the request parameters used to load a value tokeninto the wallet.

TABLE 7A Request Parameters Data Suggested Element Type LengthDescription accountid string 100  Unique identifier for a account amountdecimal N/A Amount to load on the account amountcurrency string  3Amount Type. txn-istimeoutreversal bool N/A 0, if it is not a reversalof any transaction type 1, if it is a reversal transaction.txn-uniqueidentifier string 12 Unique transaction id.

Table 7B illustrates the response parameters used to load a value tokeninto the wallet.

TABLE 7B Response Parameters Data Suggested Element Type LengthDescription accountid string 100 Unique identifier for a accountaccounttype string 50 Type of the account. balance decimal N/A Balanceavailable in the account uniqueidentifier string (numeric 12 Uniqueidentifier for the values [0-9] transaction. only) code string 7 TheStatus of the requested transaction. description string 500 The Statusdescription of the requested transaction. currency string 3 DenominationType.

If the request is for value token redemption, then in block 308, theelectronic value token transaction computer 150 accesses the electronicwallet previously determined to be associated with the authenticationinformation and examines the rules associated with the electronicwallet. In at least one embodiment, examining the rules comprisesexamining priorities of value tokens configurable by the user. Forexample, the user may prefer to use any closed loop value tokenscorresponding to the retailer originating the purchase request. If noneis found or if the token will not cover the purchase, then the user mayprefer to use an open loop value token for the remainder. As a result ofthese preferences, the closed loop value tokens may all have higherpriority than the open loop value tokens. Among the open loop valuetokens, one may have priority over another. For example, the userprefers to pay for any remainder with a credit card rather than a debitcard. In at least one embodiment, the user may configure these rules viathe Internet or mobile application and save the priorities as defaultpreferences. In an alternative embodiment, the user selects theelectronic value tokens to apply to the electronic wallet request at thePOS device, for example at a vendor or retailer location such as acheck-out lane, customer service counter, or kiosk. As such, selectingthe electronic value tokens comprises selecting value tokens with thehighest priority that, when used together, will cover the purchaseamount. As can be seen in the example, one purchase transaction has beensplit into two redemptions without compromising efficiency of thepurchase. Similarly, one or more electronic wallet transactions can besplit into two or more transactions without compromising efficiency. Inan embodiment, at least one of the electronic value tokens is associatedwith a closed loop prepaid account (e.g., an electronic prepaid, gift,or stored value card) and the rules associated with a primary walletinvoke a sub-transaction processed by a third party administratorassociated with a sub-wallet.

In at least one embodiment, examining the rules comprises examiningpercentages of the electronic wallet request to which different valuetokens should be applied and wherein applying the electronic valuetokens comprises applying the electronic value tokens to the electronicwallet request in according to the percentages. In block 310, theelectronic value token transaction computer 150 then selects, based onthe rules, value tokens in the electronic wallet that, when usedtogether, will cover the electronic wallet request. For example, theuser may configure the rules such that each purchase is split evenlybetween two credit cards. As such, selecting the electronic value tokenscomprises selecting two open loop tokens between which to split thepurchase amount. Similar to the above example, efficiency is preservedbecause where a single authorization token (e.g., only the proxy card ora mobile device) was used at the point of sale, not the two credit cardscorresponding to the electronic value tokens. Other rules can beimplemented, and the rules can be used in various combinations andpermutations with each other. The electronic value token transactionprocessing system can also implement “if-then” rules based on theinformation transmitted in the electronic wallet request. For example, apurchase at a gas station can result in a gas credit card value tokenselection, and the like. In such am embodiment, the electronic valuetoken computer 150 may query the rule(s) 802, 817, 818, and 819 of thesubject e-wallet 10 and/or sub-wallets 807 (e.g., for credit card-typeelectronic value tokens), 808 (e.g., for debit card-type electronicvalue tokens), and 809 (e.g., for stored value-type electronic valuetokens) and determine, based on transaction request information whichincludes a transaction type, e.g., purchase at a gas station, thatrule(s) established for the subject e-wallet 10 and/or sub-wallets 807,808, and 809 require that the transaction type request be firstsatisfied with a first electronic value token type, e.g. a gascard-related electronic value token 829, and upon the occasion that thesubject e-wallet 10 and/or sub-wallet(s) 807, 808, and 809 do notcomprise a sufficient amount of the first value token type to satisfythe entire transaction request, the electronic value token computer 150may satisfy the remainder of the transaction request with a secondelectronic value token type, e.g., a debit card-related electronic valuetoken 828.

The electronic value token transaction computer 150 also applies theelectronic value tokens to the electronic wallet request. In applyingthe electronic value tokens to the request, the electronic value tokentransaction computer 150 can generate and send debit and credit messagesto be performed on the accounts administered by the retailers andfinancial institutions using the appropriate account numbers, or theelectronic value token transaction computer 150 can credit or debit theaccounts directly if the electronic value token transaction computer hassuch administrative authority.

In at least one embodiment, the electronic value token transactioncomputer 150 modifies the request (e.g., applies a required format) andforwards the modified request to the appropriate one of the issuers'authorization systems 160, which receives the modified request and actsupon same, for example authorizing and/or processing the request toredeem the electronic value token and updating a datastore accordingly.The authorization system 160 is not at the same location from where theelectronic wallet request was received in at least one embodiment. Forexample, if the electronic wallet request was received from a retailstore, the authorization system may be owned and operated by theretailer, but will not be at the retail store. Rather, the authorizationsystem may be located at a data center for example. As such, neither theretail store nor the retailer in general need be aware of some or allthe contents of the wallet. In at least one embodiment, the retail storeis unaware of even the presence of the electronic wallet, as it merelyrecognizes that some transaction authorizing action has beencommunicated to its point of sale (e.g., swipe of a proxy card, digitalpersonal assistant interaction with point of sale device, entry of a PINat a keypad at point of sale, or other authorizing activity). In otherwords, access and use of the e-wallet at the point of sale is seamlessand does not require any special or custom actions in order to processthe transaction in comparison to traditional physical tender. Theissuers' authorization systems 160 sends a response message back to theelectronic value token transaction computer 150. In an alternativeembodiment where the electronic value token transaction computer 150performs the functions of the issuers' authorization systems 160, themethod may proceed directly from block 306 or 310 to block 314.

The electronic value token transaction computer 150 receives theconfirmation message from the appropriate one of the issuers'authorization systems 160 in block 312. At block 314, the electronicvalue token transaction computer 150 updates electronic wallet in theelectronic wallet unit 199 and datastore 180 to reflect that theelectronic wallet is activated and to reflect any debit, credit,addition, or deletion to/of the electronic value token(s). FIGS. 9A-Dillustrate a series of user interface screens and prompts in at leastone embodiment. For example, the user may see the illustrated promptswhen managing the user's electronic wallet via a computer connected tothe Internet, and/or kiosk 189.

A transaction log 170 may be updated by the electronic value tokentransaction computer 150 in block 316 to record the details about thetransaction. The details recorded in the transaction log may include (a)the type, time and date of the transaction, (b) whether the electronicwallet was activated, (c) the reason electronic wallet was not activatedif the request was denied, (d) the credit, debit, addition, or deletionto/of the electronic value token(s), (e) a change in rules associatedwith the electronic value token(s), (f) the identity of the vendor, (g)the identity of the issuer, (h) the location of the vendor, (i) theidentity of the terminal adding the electronic value token, (j) theidentity of the entity granting the electronic value token, and (k) anycombination thereof. The transaction log may include other information(e.g., transaction and/or authentication data) in addition to or inplace of the items enumerated above.

The electronic value token transaction computer 150, in block 318, thenforwards the confirmation message to the point of sale device 111. Theelectronic value token transaction computer 150, prior to forwarding theconfirmation message to the point of sale device 111, may modify theconfirmation message, for example as necessary to include informationthat may be printed on a receipt for the customer and/or presented on adisplay to the store clerk operating the point of sale device 111. Atblock 320, the electronic value token transaction computer 150reconciles the accounts of the various vendors, merchants, issuers, theelectronic value token transaction processing system administrator, andother entities involved with issuing, selling, redeeming, and marketingthe electronic value tokens to debit and credit appropriate accountsand, in some embodiments, initiates funds transfers between appropriatebank accounts belonging to the various entities. Alternatively,reconciliation of accounts may be performed periodically (e.g., daily,weekly, monthly, etc.) rather than after each transaction. In such anembodiment, the information from the transaction log 170 may be utilizedto reconcile the various entities involved with the sale or redemptionof various value tokens thus requiring fewer funds transfers to beinitiated. In an embodiment, information in transaction log 170 is usedto match transactions and the like. For example, grouping alltransactions from a given location or a given merchant, or groupingtransaction types (e.g., credit, debit, etc.). In various embodiments,the sequence of events depicted in may be varied, and thus may becarried out in any desired order, sequentially or simultaneously.

FIG. 5B illustrates an exemplary electronic value token transactionprocessing system 1100 in accordance with an embodiment wherein theelectronic wallet processing system comprises the electronic value tokentransaction computer 150, functioning as an electronic sub-wallettransaction processor, integrated with a primary electronic wallettransaction processor such as depicted by E-Wallet Aggregator System1000. E-Wallet Aggregator System 1000 may be further understood to havethe same functionalities, capabilities, database access, networkedconnections, and operative components as the herein described electronicvalue token transaction computer 150, and in some embodiments anelectronic value token transaction computer 150 and its associatedcomponents (e.g., electronic value token transaction processing system100) may serve as, or be substituted for, the E-Wallet Aggregator System1000. In an embodiment, the E-Wallet Aggregator System 1000 may becontrolled, maintained, operated, owned, and/or otherwise managed by acommon entity or entities which control, maintain, operate, own, and/orotherwise manage the electronic value token transaction computer 150.i.e., the primary electronic wallet transaction processor and theelectronic sub-wallet transaction processor share a common controller,maintainer, operator, owner, and/or manager. In an embodiment, theE-Wallet Aggregator System 1000 may be controlled, maintained, operated,owned, and/or otherwise managed by an entity or entities that areseparate, distinct, and/or unrelated to the entity and/or entities whichcontrol, maintain, operate, own, and/or otherwise manage the electronicvalue token transaction computer 150, i.e., the primary electronictransaction processor and the electronic sub-wallet transactionprocessor do not share a common controller, maintainer, operator, owner,and/or manager. As shown, when functioning in an electronic sub-wallettransaction processing capacity, the electronic value token transactionprocessing system 1100 comprises: (a) an electronic value tokentransaction computer 150; (b) an E-Wallet Aggregator System interface1052; (c) a datastore 180 containing an electronic wallet unit 199storing electronic value tokens, e.g., 804, 827, 828, and 829, such asaccount numbers, electronic wallet account information, value addedaward conditions (herein “value added award” is synonymous with “valueadded bonus,” “value added bonus award,” “value added award bonus,” and“value differentiation”), and other information related to adding,redeeming, and managing the electronic value tokens, as described indetail herein; (d) at least one individual issuers' authorization system160; and (e) any other unit included in the system by the electronicvalue token transaction computer administrator 151. In one embodiment,the electronic value token transaction computer 150 comprises a valueadded determination unit 153, an E-Wallet Aggregator System interface1052, a message modification unit 154, a reconciliation unit 155, anissuer system interface 156, an authorization unit 157, and a sortingunit 198. The E-Wallet Aggregator System interface 1052 provides a meansfor the electronic value token transaction computer 150 to communicatewith the E-Wallet Aggregator System 1000 via, for example, the Internet,a Public Switched Telephone Network (“PSTN”), or an independentdedicated network. Likewise, the electronic value token transactioncomputer 150 may communicate via issuer system interface 156 with theissuers' authorization system 160 via, for example, the Internet, aPublic Switched Telephone Network (PSTN), or an independent dedicatednetwork. Communications 116, 117 between the E-Wallet Aggregator Systeminterface 1052 and the E-Wallet Aggregator System 1000 andcommunications 109, 110 between the issuer system interface 156 and theissuers' authorization systems 160 may be encrypted for added securityand/or may utilize a virtual private network (“VPN”). The sorting unit198 may sort the communications into various types for routing invarious ways. For example, the sorting unit 198 may identify and sortsub-wallet requests (e.g., upon receipt of authorization informationwith a transaction request, the sorting unit 198 can route the requestedtransaction to a specific electronic sub-wallet maintained by the systemand/or to a specific section or sections maintained within theelectronic sub-wallet), balance inquiry requests, registration requests,activation requests, redemption requests, and management requests forrouting to the various units of FIG. 5B. The electronic value tokentransaction computer 150 or sorting unit 198 may also generate messagesbased on the requests for similar routing.

As can be seen in FIG. 5B, at the point of sale device 111 (typicallylocated at a vendor and/or redeeming merchant or retailer, butalternatively located at a kiosk 189 or at a user's home or office wherea personal computer is configured to act as a point of sale, for exampleduring an on-line transaction), the authentication token is interpretedby a point of sale interpretation unit 101 (e.g., a card reader). Thepoint of sale interpretation unit 101 can comprise a human, a bar codescanner, magnetic strip reader, optical character recognition device,biometric device, numerical keyboard (e.g., for entering a tokenidentification number) or other device configured to interrogate,interpret, capture, or input the data encoded in or on theauthentication token.

About contemporaneously with (or, alternatively, prior or subsequent to)the interpretation of the authentication token, a request for anelectronic wallet transaction by a point of sale transaction unit 104 ismade. The point of sale transaction unit 104 can comprise a human, anelectronic input device, a register or terminal, a computer processingunit (“CPU”), a personal computer, a personal digital assistant, smartphone, or other means of requesting or messaging interpreted by thepoint of sale interpretation unit 101 and/or point of sale processingunit 105. In some embodiments, the actions performed by the point ofsale interpretation unit 101 and the point of sale transaction unit 104may be performed by one unit capable of performing both actions thatwould be performed by the individual units, for example a point of saleregister/terminal or a personal computer during an on-line, web-basedtransaction.

The point of sale interpretation unit 101 and the point of saletransaction unit 104 communicate with the point of sale processing unit105. The point of sale processing unit 105 can comprise a CPU or othertype of processing device accepted for use in the industry. The point ofsale interpretation unit 101 communicates authentication information 102to the point of sale processing unit 105. The point of sale transactionunit 104 communicates the request 103 for an electronic wallettransaction to the point of sale processing unit 105. The point of saleprocessing unit 105 may combine this information to communicate with theE-Wallet Aggregator System 1000 (e.g., transmits a message requesting anelectronic wallet transaction along with the associated transactionand/or authentication data). In an embodiment, the point of saleprocessing unit 105 stores and/or receives from the E-Wallet AggregatorSystem 1000 (or a sub-administrator or unit associated therewith, suchas a sub-wallet administrator, e.g., electronic value token transactioncomputer 150) a transaction format associated with the POS retailerand/or associated with a given transaction type and/or value token, andsuch transaction format may be used to format the transaction request ormessage, to prompt the user for further information, or for other datagathering or transmit/receive features at the point of sale. Forexample, a user making a purchase at a retailer operates a card reader.A card reader may a display with an input device and a barcode reader ormagnetic strip scanner. The card reader may be touch sensitive and mayhave various buttons used for input. Following the card reader prompts,the user sees the options “Debit,” “Credit,” and “E-Wallet.” The userselects “E-Wallet.” The user then sees the options “Purchase,” “AddToken,” and “Delete Token.” The user selects “Purchase.” Followingadditional prompts (which in an embodiment relate to a transactionformat specific to the particular retailer of the point of sale), theuser enters a PIN number. In some embodiments, the actions performed bythe point of sale interpretation unit 101, the point of sale transactionunit 104, and the point of sale processing unit 105 may all be performedby one unit (e.g., an integrated POS device such as a computerizedregister) capable of performing all the actions that would be performedby the individual units.

The point of sale processing unit 105 is connectable to the E-WalletAggregator System 1000 via a suitable network, such as the Internet, thepublic switched telephone network (PSTN), or an independent dedicatednetwork. Each point of sale processing unit 105 has an associatedidentifier (e.g., a terminal identifier or serial number) that may betransmitted to the E-Wallet Aggregator System 1000 during the course ofconnecting the point of sale processing unit 105 to the E-WalletAggregator System 1000. Each point of sale processing unit 105 mayinclude multiple point of sale transaction units corresponding toindividual terminals each with its own terminal identification, forexample present within a given store location.

As depicted in FIG. 5B, the E-Wallet Aggregator System 1000 isconfigured to: (a) form a secure connection with the retailer/merchantand/or vendor (e.g., via the point of sale device 111), the electronicvalue token transaction computer 150, and the issuers' authorizationsystems 160; (b) to communicate with issuers' authorization systems 160to request and receive redemption or addition of value tokens intoelectronic wallets; (c) to communicate with issuers' authorizationsystems 160 to redeem all or a portion of the electronic value tokensassociated with the electronic wallet; (d) communicate with theelectronic value token transaction computer 150 to facilitatetransactions concerning value tokens residing in an electronicsub-wallet maintained by the electronic value token transactionprocessing system 1100; (e) communicate to the retailer/merchant and/orvendor (e.g., via the POS unit 111) the redemption or addition of valuetokens into electronic wallets and any information concomitant with theredemption or addition of value tokens into electronic wallets and/orsub-wallets; and (f) communicate to the retailer/merchant and/or vendor(e.g., via the POS unit 111) any reasons why transactions cannot not becompleted.

The electronic value token transaction computer 150 may comprise asingular processing unit (e.g., a centralized server), a plurality ofprocessing units (e.g., a distributed computing system with variousunits distributed and in communication with each other), or combinationsthereof, with concomitant storage capabilities, each capable of ordesignated for: accessing the datastore 180; creating a transaction log170; creating and maintaining an error log 175; communicating with theE-Wallet Aggregator System 1000; communicating with the individualissuers' authorization systems 160; processing individual value tokenand electronic wallet requests; processing redemption requests,processing value added functions to add additional cash value or add anelectronic redemption coupon for a specific product(s) or service(s),processing redemption request for electronic redemption coupons forspecific product(s) and/or service(s), and communicating with othersystems 190 capable of and authorized to communicate with the electronicvalue token transaction computer 150.

Datastore 180 maintains records of accounts associated with eachelectronic sub-wallet indicating: (a) whether each individual valuetoken has been added or redeemed, (b) whether an authentication tokenfor an individual value token has been registered, (c) records anddetails of each individual redemption request, (d) the amount remainingon the electronic value tokens, (e) rules required for redeeming theelectronic value tokens, (f) identity of the issuers of the electronicvalue tokens, (g) value added bonus awards, (h) rules for redeemingvalue added bonus awards, and (i) any combination thereof. The datastoremay also maintain records of rules required for granting a value addedbonus award to an electronic wallet or value token.

Datastore 180 also maintains records associated with each electronicwallet and/or sub-wallet indicating: (a) timing of, and otherinformation related to, registration activities; (b) timing of, andother information related to, management activities; (c) timing of, andother information related to, transaction activities; (d) rulesapplicable; (e) identity of the issuers electronic value tokens therein;(f) identity of sub-wallets associated therewith; (g) any other recordsrequested by issuers, merchants, vendors, advertisers, users, or otherinterested parties; and (h) any combination thereof. While a singledatastore 180 is shown, it should be understood that a plurality ofdatastores may be employed, and relevant data divided among thedatastores in any suitable manner to meet the various processes andobjectives described herein. Also, the various data may be associatedwith one or more datastores closely coupled to and/or located inproximity to one or more sub-units, sub-processors, third partyprocessors, and the like associated with the electronic value tokentransaction computer 150, and such datastores preferably have data usedby such sub-units, sub-processors, and third party processors.

The electronic value token transaction computer 150 is also configuredto generate and maintain a transaction log 170 of all activity involvingthe electronic value token transaction computer 150. The transaction logmay comprise a detailed summary of transaction types such as: (a)requested value token additions; (b) requested value token sales; (c)requested value token redemptions; (d) requested value token exchanges;(e) the monetary amount ascribed to value token additions; (f) themonetary amount ascribed to value token redemptions; (g) the monetaryvalue ascribed to value token exchanges; (h) the value added amounts,products, or services additions; (i) the value added amounts, products,or services redemptions; (j) the time the electronic value tokens wereadded; (k) the time the electronic value tokens were redeemed; (l) thetransaction or communication performed with the issuer for adding valuetokens; (m) the transaction or communication performed with the issuerfor redeeming value tokens; (n) the PIN communicated to the vendor inresponse to a request to add a value token requiring the input of a PINfor use; (o) e-wallet registration; (p) e-wallet set-up activities; (q)e-wallet transaction activities; (r) e-wallet savings activities; (s)e-wallet management activities; (t) any other information the electronicvalue token transaction computer administrator 151 directs theelectronic value token transaction computer 150 to maintain as a logentry; and (u) any combination thereof.

The information contained in the transaction log 170 may be used fordata mining purposes, e.g., to generate reconciliation reports,settlement reports, payment reports, audit reports, e-walletregistration reports, e-wallet management reports, e-wallet usagereports, e-wallet savings reports, electronic value token purchasereports, electronic value token redemption reports, electronic valuetoken exchange reports, electronic value token sale reports, or otherforms of information aggregation for the benefit of, use by, or forprovision to, the electronic value token transaction administrator 151,the datastore administrator 181, the E-Wallet Aggregator System 1000(e.g., for communication to vendors or other purposes), vendors,issuers, issuers' authorization systems 160, redeeming merchants, orother interested parties. For example, the transaction log 170 containsinformation about each transaction performed by electronic value tokentransaction computer 150 (and any sub-components thereof) and may beutilized by the reconciliation unit 155 when reconciling accountsbelonging to various E-Wallet Aggregator System 1000 associated vendors,merchants, issuers, as well as vendors, merchants, and issuers notassociated with the E-Wallet Aggregator System 1000, and also theelectronic value token transaction processing system administrator 151.Additional data mining considerations that may be recorded, analyzed,and/or provided interested parties (e.g., vendors, merchants, issuers,advertisers, etc.) include data about: (i) the purchase habits ofe-wallet users; (ii) electronic value token purchases, sales,redemptions, and exchanges; (iii), special offer and/or value addedactivities; (iv) loyalty-related activities; and (v) savings-relatedactivities, all of which can be used for marketing, inventory, and otherpurposes.

Oversight and maintenance of the electronic value token transactioncomputer is performed by the electronic value token transaction computeradministrator 151. Although not required, in an alternative embodiment,the electronic value token transaction computer administrator 151 mayalso function as the datastore administrator 181. The electronic valuetoken transaction computer 150 is configured to generate and maintain anerror log of all transactions that were not completed and reasonstherefore. In some embodiments, the error log is administered by theelectronic value token transaction computer administrator 151.

The electronic value token transaction computer 150 is also configuredto communicate with other entities 190 authorized to access theelectronic value token transaction processing system and specificallyauthorized to access the electronic value token transaction computer150. These other entities may comprise E-Wallet Aggregator System 1000,third party payment management systems, third party audit systems,issuer affiliated entities, vendor affiliated entities, redeemingmerchants or redeeming merchant affiliated entities, financialinstitutions such as banks, credit card agencies, or credit unions, orany other entity provided access by the electronic value tokentransaction computer administrator 151 or other entity having authorityto grant access.

In an embodiment, the transaction request from the E-Wallet AggregatorSystem 1000 may contain one or more of the following pieces ofinformation: (a) authentication information, (b) point of sale terminalidentification, (c) amount to be credited or debited, (d) the time ofthe request, (e) the date of the request, (f) identification of theissuer, (g) identification of the vendor, (h) location of vendor, (i)identification of the product(s) and/or service(s) being purchased, (j)an activation or deactivation request, (k) a wallet management functionsuch as addition of a value token, deletion of a value token, exchangeof a value token, changing management or processing rules associatedwith one or more value tokens, partitioning a wallet into sub-wallets orvice-versa, etc., (l) and any combination thereof. However, theinformation contained within the request is not limited to theenumerated list but may comprise other items in addition to the itemsenumerated or in place of the items enumerated above.

Upon receipt of the electronic wallet transaction request from theE-Wallet Aggregator System 1000, and identification and sorting as suchby the sorting unit 198, the electronic value token transaction computer150 accesses the electronic wallet unit of datastore 180. The electronicvalue token transaction computer 150 processes the information containedin the datastore 180 and communicates 109, 110 with the individualissuers' authorization systems 160 to effectuate management of theelectronic value tokens and corresponding accounts. The messagemodification unit may adjust the messages and requests so that multipleunits, sub-components/processors, or third party administrators canrecognize and correctly interpret the messages. For example, after theelectronic value token transaction computer 150 determines theindividual issuers' authorization systems 160 associated with therequest, the message modification unit 154 accesses the database 180 todetermine the appropriate transaction messaging formats for eachindividual issuers' authorization systems 160 and then formats thesubsequent communications to said individual issuers' authorizationsystems 160 using the individual issuers' authorization systems 160specified/preferred transaction format and vocabulary. The electronicvalue token transaction computer 150 can also provide the appropriatemessaging formatting information, e.g., a template, to the E-WalletAggregator System 1000 to facilitate that system's processing ofinformation related to the request. The electronic value tokentransaction computer's 150 communication with the individual issuers'authorization systems 160 may occur simultaneously or independently. Theelectronic value token transaction computer 150 is connectable to theindividual issuers' authorization systems as via a suitable network,such as the PSTN, the Internet, or an independent dedicated network. Theelectronic value token transaction computer 150 is configured to sendand/or receive communication 110 from the issuers' authorization systems160 concerning the status of the electronic value tokens.

The reconciliation unit 155 reconciles the accounts of various issuers,selling vendors, and/or redeeming merchants, to credit and debitappropriate merchants, vendors, the electronic value token transactionprocessing system administrator, and issuers with the value of varioustransactions to reflect which entities received value from which otherentities. For example, if a vendor A sells a value token issued byissuer B for a specified amount and receives payment from a user whoadds the electronic value token to the user's electronic wallet, theselling vendor receives a percentage (e.g., retains a percentage) of thepurchase amount and/or a predetermined amount, the E-Wallet AggregatorSystem 1000 and/or the electronic value token system administratorreceives a percentage of the purchase amount and/or predetermined amountfor processing the transaction, and the issuer receives the remainder.If a value token issued by issuer Y is redeemed at merchant X topurchase items, then the amount redeemed is debited to the issuer Y andcredited to the merchant X, sometimes minus a transaction fee collectedby the issuer and/or a transaction or processing fee collected by theelectronic value token transaction processing system administrator.

Authorization unit 157 is utilized when the electronic value tokentransaction computer 150 is also the authorizing system such that theelectronic value token transaction computer 150 authorizes electronicsub-wallet requests rather than transmitting the request to the issuers'authorization systems 160 for authorization. The authorization unit 157may perform the same and/or different functions as described forauthorization systems 160 and vice-versa.

The authorization unit 157 will validate the formatting of the wallet(e.g., primary or sub-wallet) transaction request received from theE-Wallet Aggregator System 1000. In other words, the authorization unit157 will check the data fields in the request to confirm that the fieldsare populated with data and that the data is in the correct format(e.g., length, alphanumeric format). If the request is improperlyformatted, the authorization unit 157 will reject the request, or insome embodiments may retrieve the proper format (e.g., from a formatdatabase) and modify the transaction request to comply with the properformat. The authorization unit 157 also performs various validationchecks on the transaction request. The authorization unit 157 verifiescard-related transaction information based on an analysis of severalcriteria, such as: 1) determining that the UPC code for the product ispresent in the datastore 180 (or other datastore such as an issuer'sdatabase) for the electronic value token transaction processing system1100; 2) determining that the value amount of the requested transactioncorresponds to the customer's payment for the subject transactionrequest, e.g., whether the UPC information identifies the card as a$25.00 card and that the corresponding transaction request includes a$25.00 payment by the customer; 3) determining that the UPC informationidentifies the card as being a type of card available for processing bythe requesting merchant; and 4) determining that the Bank IdentificationNumber (“BIN”) of the card (i.e., the first six digits of the card'sidentification number), which identifies the card issuer, corresponds tothe UPC information identifying the card issuer.

The authorization unit 157 may also verify transactions based on othercriteria such as transaction velocity (number/amount per unit time). Forexample, if a card processor is concerned that multiple voidtransactions are indicative of fraudulent activity, the card processorcould ask that the electronic value token transaction processing system1100 monitor the number of void transactions requested and rejecttransactions from terminals that exceed a pre-selected amount of voidtransactions per unit time. Lastly, the authorization unit 157 may beconfigured to reject transaction requests in the event that theinformation received by the authorization unit 157 is unintelligible.

If the request is properly formatted and is validated as describedabove, the electronic value token transaction computer 150 may transmitdetails of transactions to the issuers' authorization systems ratherthan authorization requests. Also, in some embodiments, the issuer, theauthorizing system 9 e.g., authorization unit 157), and the transactioncomputer are part of the same entity and, in such an embodiment, therewould be no issuers' authorization systems 160 or the issuers'authorization systems 160 would be under common control with the otherunits of the electronic value token transaction computer 150 (forexample, a commonly owned and operated computing system, that may becentralized (e.g., part of a centralized data center) and/or distributedwithin a commonly owned or controlled system or network). Furthermore,it should be noted that although units associated with the electronicvalue token transaction computer 150 (e.g., units 152-157) are depictedas various units within a single data processing system for illustrationand conceptual purposes, one or more of units 152-157 could beimplemented on separate computers, systems, or servers in a distributeddata processing environment.

An exemplary process utilized by an electronic value token transactioncomputer 150 for facilitating a purchase using an electronic wallet inaccordance with an e-wallet transaction comprising an electronicsub-wallet maintained by a third party electronic value tokentransaction computer which maintains the sub-wallet as part of arelationship with a primary e-wallet system provider, e.g., the E-WalletAggregator System 1000, embodiment is depicted in FIG. 7B. Such anembodiment may be exemplified by the e-wallet transaction processingrequest being initially received by the E-Wallet Aggregator System 1000and performed in part by the electronic value token computer 150. Theactions depicted can be performed in the order shown or in a differentorder, and two or more of the actions can be performed in parallel.

In block 301, the E-Wallet Aggregator System 1000 receives a request ormultiple requests from the point of sale 111. In at least one embodimentthe requests may comprise an electronic wallet transaction request, abalance inquiry request, a registration request, an activation request,or a redemption request, a wallet management request, and contains oneor more of the following: (a) identity of the terminal, (b)authentication information, (c) the amount of the purchase, (d) theidentity of the electronic value token issuer, (e) the identity of thevendor, (f) the identity of the location, (g) the time of the request,(h) the date of the request, (i) information expressly identifying therequest as an e-wallet transaction request (e.g., transaction typedata); (j) information identifying a primary e-wallet, sub-wallet(s), ora combination thereof; (k) any other transaction and/or authenticationdata described herein; and (l) any combination thereof. The request atblock 301 may comprise other information, requests or functions, forexample of the types described herein, in addition to or in place of theabove enumerated items. In at least one embodiment, the authenticationinformation is based on an authentication token selected from the groupconsisting of proxy card and cellular phone.

Continuing with the process of block 301, the E-Wallet Aggregator System1000 may determine that a portion of the requested e-wallet transactionmay be processed via the E-Wallet Aggregator System 1000 while anotherportion of the requested e-wallet transaction implicates a sub-walletwhich is maintained by a third party administrator, e.g., electronicvalue token transaction computer 150. If the electronic wallettransaction request information received by the E-Wallet AggregatorSystem 1000 indicates that the transaction request will require/involvea sub-wallet maintained by a third party administrator's system to fullyeffectuate a response to the transaction request, and the rulesapplicable to the associated primary e-wallet maintained by the E-WalletAggregator System 1000 so dictate, the E-Wallet Aggregator System 1000processes the original request, generates a new request, generates asub-request, or modifies the original request, to send to the sub-walletwhich is maintained in association with the primary electronic wallet,e.g., the primary electronic wallet sends the original request, the newrequest, the sub-request, or the modified original request to theelectronic value token transaction computer 150, which maintains theindicated sub-wallet. In processing the original request, generating thenew request, generating the sub-request, or modifying the originalrequest to send to the sub-wallet, the E-Wallet Aggregator System 1000may (i) apply its own logic to the e-wallet transaction request; (ii)apply rules stored in the primary wallet (e.g., rules formulated by theprimary e-wallet provider, the primary e-wallet user, or a combinationthereof); (iii) apply rules received with the transaction request fromthe point of sale 111 (e.g., contemporaneous rules submitted with therequest by the user of the primary electronic wallet and/or electronicsub-wallet); (iv) or any combination thereof.

In block 303, the electronic value token transaction computer 150receives a request or multiple requests from the E-Wallet AggregatorSystem 1000. In at least one embodiment the requests may comprise anelectronic sub-wallet request, a balance inquiry request, a registrationrequest, an activation request, or a redemption request, a sub-walletmanagement request, and contains one or more of the following: (a)identity of the terminal, (b) authentication information, (c) the amountof the purchase, (d) the identity of the electronic value token issuer,(e) the identity of the vendor, (f) the identity of the location, (g)the time of the request, (h) the date of the request, (i) informationexpressly identifying the request as an e-wallet transaction request(e.g., transaction type data); (j) information identifying a primarye-wallet, sub-wallet(s), or a combination thereof; (k) any othertransaction and/or authentication data described herein; and (l) anycombination thereof. The request at block 303 may comprise otherinformation, requests or functions, for example of the types describedherein, in addition to or in place of the above enumerated items. In atleast one embodiment, the authentication information is based on anauthentication token selected from the group consisting of proxy cardand cellular phone. Using the identity of the proxy card and/or cellularphone, embedded transactions may be correctly formatted forcommunication with the pertinent electronic value token issuers of thesubject transaction request.

Using information received from the E-Wallet Aggregator System 1000pursuant to the transaction request and from information obtained fromdatastore 180, in block 304, the electronic value token transactioncomputer 150 determines whether the request is an electronic sub-walletrequest containing valid authentication information and whether therequest is for redemption of a value token(s), addition of a valuetoken(s), deletion of a value token(s), or other management of theelectronic sub-wallet. The electronic sub-wallet request may comprise abank identification number (“BIN”) as part of the authenticationinformation. The sorting unit may decode the BIN number or otherwiseverify that the request is an electronic sub-wallet request concerningan electronic value token residing in the indicated sub-wallet.

Using information contained within the electronic wallet transactionreceived from the E-wallet Aggregator System 1000, and/or frominformation obtained from datastore 180, in block 324, the electronicvalue token transaction computer 150 identifies/determines thesub-wallet(s), and/or locations of said sub-wallet(s)indicated/necessary to effectuate the received e-wallet transactionrequest. If the authorization information received indicates therequested e-wallet transaction involves a sub-wallet maintained by theelectronic value token transaction computer 150, the electronic valuetoken transaction computer 150 may (i) apply its own logic to therequest; (ii) apply rules stored in a sub-wallet (e.g., rulesestablished by the electronic value token transaction processing systemadministrator, the sub-wallet user, or a combination thereof); (iii)apply rules stored in a sub-sub-wallet (e.g., rules established by theelectronic value token transaction processing system administrator, thesub-sub-wallet user, or a combination thereof) (iv) apply rules receivedwith the request from the point of sale 111 (e.g., contemporaneous rulessubmitted with the request by the user of the primarye-wallet/sub-wallet); (v) or any combination thereof.

For example, an embodiment may include the electronic value tokentransaction computer 150 determining that the entire request receivedfrom the E-Wallet Aggregator System 1000 is related to value tokenscontained in a singular sub-wallet. Upon receipt of the request, theelectronic value token transaction computer 150 will query itsauthorization unit 157 (as described more fully herein), its datastore180, the E-Wallet unit 199, and any other necessary unit to determinewhether the sub-wallet comprises value tokens capable of meeting thesubject request (e.g., whether the sub-wallet contains value tokensassociated with vendors, merchants, and/or issuers related to therequested transaction). Such determination may be performed by comparingelectronic value token identifications, user IDs, requested transactiontypes. The electronic value token transaction computer 150 willsubsequently evaluate the manner in which the electronic value tokensavailable in the sub-wallet corresponding to the request will be appliedunder the sub-wallet's rules and/or rules received with the request, andperform or refuse to perform the requested transaction and/ortransactions.

Another embodiment may include the electronic value token transactioncomputer 150 determining that the entire request received from theE-Wallet Aggregator System 1000 is related to value tokens contained ina sub-sub-wallet. Upon receipt of the request, the electronic valuetoken transaction computer 150 will query its authorization unit 157 (asdescribed more fully herein), its datastore 180, the E-Wallet unit 199,and any other necessary unit to determine whether the sub-sub-walletcomprises value tokens capable of meeting the subject request (e.g.,whether the sub-sub-wallet contains value tokens associated withvendors, merchants, and/or issuers related to the requestedtransaction). Such determination may be performed by comparingelectronic value token identifications, user IDs, requested transactiontypes. The electronic value token transaction computer 150 willsubsequently evaluate the manner in which the electronic value tokensavailable in the sub-sub-wallet corresponding to the request will beapplied under the sub-sub-wallet's rules and/or rules received with therequest, and perform or refuse to perform the requested transactionand/or transactions.

In another example, an embodiment may include the electronic value tokentransaction computer 150 determining that a portion of the requestreceived from the E-Wallet Aggregator System 1000 is related toelectronic value tokens residing in a sub-wallet while another portionof the request is related to electronic value tokens residing in asub-sub-wallet. Such determination may be made by evaluating therequested transaction type, the electronic value token identification,or any other methods for determining transaction allocation. Theelectronic value token transaction computer 150 will evaluate the mannerin which the electronic value tokens available in the sub-walletcorresponding to the request will be applied under the sub-wallet'srules (as those rule may affect payment methods to be employed which arelocated in the sub-wallet), the electronic value token transactioncomputer 150 will evaluate the manner in which the electronic valuetokens available in any applicable sub-sub-wallet corresponding to therequest will be applied under such sub-sub-wallet's rules and/or rulesreceived with the request, and perform or refuse to perform therequested transaction and/or transactions.

In an exemplary embodiment, at block 324, the electronic value tokentransaction computer 150 may identify, in response to a receivedtransaction request, one or more value tokens in a sub-wallet and one ormore electronic value tokens in a sub-sub-wallet that, when usedtogether, will cover the entirety of the requested e-wallet transaction.Moreover, one of the electronic value tokens located in the sub-walletor sub-wallet may be an electronic representation of a loyalty card andanother electronic value token located in either the same or differentlocation of said loyalty card value token may be an electronicrepresentation of a retailer's gift card. In such an example, theelectronic value token transaction computer 150 can effectuate thecoincidental use of the “loyalty card” token and the “retailer's giftcard” token, regardless of the tokens' locations in the sub-walletand/or sub-sub-wallet(s) to allow for an enhanced user benefit asopposed to not coincidentally applying the value of the “retailer's giftcard” token and the “loyalty card” token for the transaction, e.g., a 5%increase in the value of the “retailer's gift card” token or loyaltypoint bonus applied to the “loyalty card” token for the use of the“retailer's gift card” token.

An electronic value token may be associated with a closed loop accountor open loop account. A closed loop account typically expires after thefunds in the account have been depleted, e.g. a gift card account. Anopen loop account does not typically expire. Rather, there is may be anongoing obligation for various entities to credit and debit the account,e.g. a branded credit card account or debit card account such as Visa orMastercard. Closed loop accounts are often associated directly withretailers while open loop accounts are often associated with financialinstitutions (e.g., Chase or Citi issued Visa). In at least oneembodiment, the electronic value tokens comprise closed loop accountnumbers and open loop account numbers. The closed loop account numbersare associated with retailers able to debit or credit closed loopaccounts associated with the closed loop account number. The open loopaccount numbers are associated with financial institutions able to debitor credit open loop accounts associated with the open loop accountnumbers. The electronic value token may have an expiration date orspecified dates of use that are different from any other value tokens.Furthermore, the electronic value tokens may identify specificmerchants, locations, and/or products with which the electronic valuetokens may be utilized.

If the request is for electronic value token addition, then in block306, the electronic sub-wallet is created (if not already created) andthe electronic value token is added to the electronic sub-wallet. Thefollowing Tables include elements, parameters, and information includedin e-wallet transaction communications and used by the electronic valuetoken transaction computer 150 to facilitate and effectuate electronicsub-wallet transactions as part of an coincidental primary e-wallettransaction being processed by a primary e-wallet transaction processingsystem, e.g. the E-Wallet Aggregator System 1000.

Table 8A illustrates request parameters requested to create a sub-walletin at least one embodiment. Table 8B illustrates response parametersrequested to create a sub-wallet in at least one embodiment.

TABLE 8A Request Parameters Data Suggested Element Type LengthDescription primaryewalletauth string variable Authorization/ID ofprimary e-wallet provider (e.g., Google or PayPal) accounttype String200  Account Type loadamt decimal N/A Amount to be loaded into thewallet account loadamtcurrency string  3 Denomination Type.txn-uniqueidentifier string 12 Unique transaction id.

TABLE 8B Response Parameters Element Data Type Description accountidstring Unique identifier for a account accounttype string Type of theaccount. currency string Denomination Type. balance decimal Balanceavailable in the account uniqueidentifier string The unique identifieridentifies a (numeric) transaction. code string The Status of therequested transaction. description string The Status description of therequested transaction.

The electronic value token transaction computer 150 preferably allocatesmemory for the electronic sub-wallet and value token(s) and associatesthe account number with the electronic sub-wallet and/or authenticationinformation stored in the electronic wallet unit 199 by storing thepieces of information in a data structure on the datastore 180. Table 9illustrates the parameters for a gift card value token in at least oneembodiment.

TABLE 9 Element and Suggested Description Data Type Lengthstatusinfo.status.code String 7 statusinfo.status.description String 500card.retailer.id Integer String 11 card.retailer.name String 100card.number String 50 card.securitycode String 50 card.expirydateInteger String 6 card.activationdate Date String 20 card.initialbalanceDecimal String 10 card.currentbalance Decimal String 10card.currentbalanceasof Date String 20 card.customerservice.phone String20 card.customerservice.website String 256 card.currency String 3

Table 10 illustrates more detailed parameters for a gift card electronicvalue token in an alternative embodiment, including the designation ofassociated sub-wallet(s) and/or sub-sub-wallet(s).

TABLE 10 Element and Suggested Description Data Type Lengthcard.retailer.id Integer String 11 card.retailer.name String 100card.number String 50 card.securitycode String 50 card.expirydateInteger String 6 card.registeredto String 10 card.activationdate DateString 20 card.initialbalance Decimal String 10card.islookedupinitialbalance String 1 card.currentbalance DecimalString 10 card.islookedupcurrentbalance String 1card.customerservice.phone String 20 card.customerservice.website String256 card.notes String 500 card.nickname String 100 card.currency String3 card.user.firstname String 50 card.user.lastname String 50card.user.address.line1 String 50 card.user.address.line2 String 50card.user.address.city String 50 card.user.address.state String 50card.user.address.zip String 5 card.user.phone.number String 10card.user.email.address String 128 card.additionalinfo1 String 300card.additionalinfo2 String 300 card.additionalinfo3 String 300wallet.id Integer String 10 Collection of folders wallet.folder.1.idInteger String 10 wallet.folder.1.name String 100 wallet.folder.2.idInteger String 10 wallet.folder.2.name String 100 [. . . More folders]

The request, however, may be modified for other reasons unrelated to theadd token decision and forwarded to the appropriate one of the issuers'authorization systems 160 as part of the reconciliation process, forexample the request could concern redemption, deletion, reloading value,added value, balance inquiry, or a combination thereof, each of whichwould be communicated to the issuers' authorization systems 160 forreconciliation.

Table 11 illustrates formatting for authentication communication.

TABLE 11 Element and Description Data Type client_ref_id Stringsignature String timestamp String(in the format yyMMddHHmmssSSSz) nonceString encryption_type String usertoken String uuid String user_ipString channel String

Each request is authenticated using the signature, a user isauthenticated with username/password or open id, the session isvalidated using the user token. A client may send client_ref_id,timestamp, nonce, encryption_type, channel, user_ip, signature,optionally usertoken with each request to be able to validate eachmessage.

Table 12 illustrates the parameters used to retrieve a user's wallet.

TABLE 12 Element Data Type Description accountid string Uniqueidentifier for a account accounttype string Type of the account.currency string Denomination Type. balance decimal Balance available inthe account code string The Status of the requested transaction.description string The Status description of the requested transaction.

Table 13A illustrates the request parameters used to redeem value from atoken in the sub-wallet.

TABLE 13A Request Parameters Data Suggested Element Type LengthDescription accountid String 100  Unique identifier for the accountredamt decimal N/A Amount to redeem from the account redamtcurrencystring  3 Amount Type. txn-uniqueidentifier string 12 Unique transactionid. txn-istimeoutreversal bool N/A 0, if it is not a reversal of anytransaction type 1, if it is a reversal transaction.

Table 13B illustrates the response parameters used to redeem value froma token in the sub-wallet.

TABLE 13B Response Parameters Data Suggested Element Type LengthDescription accountid string 100 Unique identifier for a accountaccounttype string 50 Type of the account. currency string 3Denomination Type. balance decimal N/A Balance available in the accountuniqueidentifier string 12 Unique identifier for the transaction. codestring 7 The Status of the requested transaction. description string 500The Status description of the requested transaction.

Table 14A illustrates the request parameters used to load a value tokeninto the sub-wallet.

TABLE 14A Request Parameters Data Suggested Element Type LengthDescription accountid string 100  Unique identifier for a account amountdecimal N/A Amount to load on the account amountcurrency string  3Amount Type. txn-istimeoutreversal bool N/A 0, if it is not a reversalof any transaction type 1, if it is a reversal transaction.txn-uniqueidentifier string 12 Unique transaction id.

Table 14B illustrates the response parameters used to load a value tokeninto the sub-wallet.

TABLE 14B Response Parameters Data Suggested Element Type LengthDescription accountid string 100 Unique identifier for a accountaccounttype string 50 Type of the account. balance decimal N/A Balanceavailable in the account uniqueidentifier string (numeric 12 Uniqueidentifier for the values [0-9] transaction. only) code string 7 TheStatus of the requested transaction. description string 500 The Statusdescription of the requested transaction. currency string 3 DenominationType.

If the request is for electronic value token redemption, then in block308, the electronic value token transaction computer 150 accesses theelectronic sub-wallet previously associated with the authenticationinformation and examines the rules associated with the electronicsub-wallet. In at least one embodiment, examining the rules comprisesexamining priorities of value tokens configurable by the user. Forexample, the user may prefer to use any closed loop value tokenscorresponding to the retailer originating the purchase request. If noneis found or if the token will not cover the purchase, then the user mayprefer to use an open loop value token for the remainder. As a result ofthese preferences, the closed loop value tokens may all have higherpriority than the open loop value tokens. Among the open loop valuetokens, one may have priority over another. For example, the userprefers to pay for any remainder with a credit card rather than a debitcard. In at least one embodiment, the user may configure these rules viathe Internet or mobile application and save the priorities as defaultpreferences. In an alternative embodiment, the user selects theelectronic value tokens to apply to the electronic wallet request in atthe POS device, for example at a vendor or retailer location such as acheck-out lane, customer service counter, or kiosk. As such, selectingthe electronic value tokens comprises selecting value tokens with thehighest priority that, when used together, will cover the purchaseamount. As can be seen in the example, one purchase transaction has beensplit into two redemptions without compromising efficiency of thepurchase. Similarly, one or more electronic wallet transactions can besplit into two or more transactions without compromising efficiency.

In at least one embodiment, examining the rules comprises examiningpercentages of the electronic sub-wallet request to which differentelectronic value tokens should be applied and wherein applying theelectronic value tokens comprises applying the electronic value tokensto the electronic sub-wallet request in according to the percentages. Inblock 310, the electronic value token transaction computer 150 thenselects, based on the rules, value tokens in the electronic sub-walletthat, when used together, will cover the electronic sub-wallet request.For example, the user may configure the rules such that each purchase issplit evenly between two credit cards. As such, selecting the electronicvalue tokens comprises selecting two open loop tokens between which tosplit the purchase amount. Similar to the above example, efficiency ispreserved because where a single authorization token (e.g., only theproxy card or a mobile device) was used at the point of sale, not thetwo credit cards corresponding to the electronic value tokens. Otherrules can be implemented, and the rules can be used in variouscombinations and permutations with each other. The electronic valuetoken computer 150 can also implement “if-then” rules based on theinformation transmitted in the electronic sub-wallet request. Forexample, a purchase at a gas station can result in a gas credit cardvalue token selection, and the like. In such am embodiment, theelectronic value token computer 150 may query the rule(s) 802, 817, 818,and 819 of the subject e-wallet 10 and/or sub-wallets 807 (e.g., forcredit card-type electronic value tokens), 808 (e.g., for debitcard-type electronic value tokens), and 809 (e.g., for stored value-typeelectronic value tokens) and determine, based on transaction requestinformation which includes a transaction type, e.g., purchase at a gasstation, that rule(s) established for the subject e-wallet 10 and/orsub-wallets 807, 808, and 809 require that the transaction type requestbe first satisfied with a first electronic value token type, e.g. a gascard-related electronic value token 829, and upon the occasion that thesubject e-wallet 10 and/or sub-wallet(s) 807, 808, and 809 do notcomprise a sufficient amount of the first value token type to satisfythe entire transaction request, the electronic value token computer 150may satisfy the remainder of the transaction request with a secondelectronic value token type, e.g., a debit card-related electronic valuetoken 828.

The electronic value token transaction computer 150 also applies theelectronic value tokens to the electronic sub-wallet request. Inapplying the electronic value tokens to the request, the electronicvalue token transaction computer 150 can generate and send debit andcredit messages to be performed on the accounts administered by theretailers and financial institutions using the appropriate accountnumbers, or the electronic value token transaction computer 150 cancredit or debit the accounts directly if the electronic value tokentransaction computer has such administrative authority.

In at least one embodiment, the electronic value token transactioncomputer 150 modifies the request and forwards the modified request tothe appropriate one of the issuers' authorization systems 160, whichreceives the modified request and acts upon same, for exampleauthorizing and/or processing the request to redeem the electronic valuetoken and updating a datastore accordingly. The authorization system 160is not at the same location from where the electronic sub-wallet requestwas received in at least one embodiment. For example, if the electronicsub-wallet request was received from a retail store, the authorizationsystem may be owned and operated by the retailer, but will not be at theretail store. Rather, the authorization system may be located at a datacenter for example. As such, neither the retail store nor the retailerin general need be aware of some or all the contents of the sub-wallet.In at least one embodiment, the retail store is unaware of even thepresence of the electronic wallet, as it merely recognizes that sometransaction authorizing action has been communicated to its point ofsale (e.g., swipe of a proxy card, digital personal assistantinteraction with point of sale device, entry of a PIN at a keypad atpoint of sale, or other authorizing activity). The issuers'authorization systems 160 sends a response message back to theelectronic value token transaction computer 150. In an alternativeembodiment where the electronic value token transaction computer 150performs the functions of the issuers' authorization systems 160, themethod may proceed directly from block 306 or 310 to block 314.

The electronic value token transaction computer 150 receives theconfirmation message from the appropriate one of the issuers'authorization systems 160 in block 312. At block 314, the electronicvalue token transaction computer 150 updates electronic sub-wallet inthe electronic wallet unit 199 and datastore 180 to reflect that theelectronic sub-wallet is activated and to reflect any debit, credit,addition, or deletion to/of the electronic value token(s). FIGS. 9A-Dillustrate a series of user interface screens and prompts in at leastone embodiment. For example, the user may see the illustrated promptswhen managing the user's electronic wallet via a computer connected tothe Internet, and/or kiosk 189.

A transaction log 170 may be updated by the electronic value tokentransaction computer 150 in block 316 to record the details about thetransaction. The details recorded in the transaction log may include (a)the time and date of the transaction, (b) whether the electronicsub-wallet was activated, (c) the reason electronic sub-wallet was notactivated if the request was denied, (d) the credit, debit, addition, ordeletion to/of the electronic value token(s), (e) a change in rulesassociated with the electronic value token(s), (f) the identity of thevendor, (g) the identity of the issuer, (h) the location of the vendor,(i) the identity of the terminal adding the electronic value token, (j)the identity of the entity granting the electronic value token, (k)identity of the E-Wallet Aggregator System 1000 from which thesub-wallet request was received, (l) communications between theelectronic value token transaction computer 150 and the E-WalletAggregator System 1000, and (m) any combination thereof. The transactionlog may include other information in addition to or in place of theitems enumerated above.

The electronic value token transaction computer 150, in block 319, thenforwards the sub-wallet transaction results and associated informationin the form of a confirmation message to the E-Wallet Aggregator System1000. The electronic value token transaction computer 150, prior toforwarding the confirmation message to the E-Wallet Aggregator System1000, may modify the confirmation message as necessary to includeinformation that may be printed on a receipt for the customer and/orpresented on a display to the store clerk operating the point of saledevice 111. At block 320, the electronic value token transactioncomputer 150 reconciles the accounts of the various vendors, merchants,issuers, the electronic value token transaction processing systemadministrator, and other entities involved with issuing, selling, andmarketing the electronic value tokens involved in the sub-wallet requestto debit and credit appropriate accounts and, in some embodiments,initiates funds transfers between appropriate bank accounts belonging tothe various entities. Alternatively, reconciliation of accounts may beperformed periodically (e.g., daily, weekly, monthly, etc.) rather thanafter each transaction. In such an embodiment, the information from thetransaction log 170 may be utilized to reconcile the various entitiesinvolved with the sale or redemption of various value tokens thusrequiring fewer funds transfers to be initiated. In various embodiments,the sequence of events depicted in may be varied, and thus may becarried out in any desired order, sequentially or simultaneously.

FIG. 5C illustrates an embodiment of the electronic value tokentransaction processing system 1200 wherein the electronic value tokentransaction computer 150 communicates with both the point of sale 111and the E-Wallet Aggregator System 1000. Thus, the electronic valuetoken transaction computer 150 may function as both a primary electronicwallet transaction processor and an electronic sub-wallet transactionprocessor as described in detail above with respect to FIGS. 5A and 5B.

Electronic wallet management may be carried out via a variety of userinterfaces such as smart phone application, personal computerapplications, website based applications, point of sale terminals,dedicated terminals at stores or other locations, such as kiosks.

In at least one embodiment, a user can perform numerous functions viathe World Wide Web from a computer or mobile phone such as electronicwallet management functions (e.g., balance inquiry, managing loyaltyand/or other bonus-type programs); exchange of value tokens such as (i)replace value token in e-wallet with value token not currently presentin e-wallet, (ii) exchange between different wallets (such as placing anelectronic value token from a sub-wallet configured to allow redemptionactivities into a sub-wallet configured for savings activities withlimited redemption possibilities), and (iii) exchange with another user;purchase electronic value tokens to be placed in e-wallet; opt in or optout of receiving targeted promotional offers and materials; and paymentfunctions such as splitting the tender of payment between availableelectronic value tokens in the e-wallet.

Regarding possible exchange possibilities, a user may exchange a valuetoken associated with a retailer that the user is unlikely to frequentwith a value token associated with a retailer that the user is likely tofrequent. Similarly, users may swap, sell, gift, or re-gift value tokensor bundles of value tokens to each other.

Via e-wallet management functionalities, a user can: (i) determine theamount of value associated with each value token such as reward points,dollar amounts, etc.; (ii) check expiration dates on value tokens,purchase value tokens for others as gifts, and receive notificationsfrom specific retailers; (iii) create, register, and delete theirelectronic wallet or specific value tokens in their electronic wallet;(iv) request that the e-wallet provide or make available a physicalrepresentation of an electronic value token in the user's electronicwallet (e.g., in an embodiment, a print-on-demand service is provided toallow the user to print out a chit, coupon, check, or other physicalrepresentation of an electronic value token at a kiosk 189 or otheraccessible printer); and (v) allow the e-wallet to send the userspecific value tokens, e.g., by using a GPS service in the user's mobilephone, or via integration with the user's SMS services.

In at least one embodiment, the user's electronic wallet is integratedwith the user's social network services such as Facebook and Twitter.Accordingly, the user can perform management functions via socialnetwork platforms or receive value tokens via social network platforms.Full or partial information about the user's electronic wallet can bemade available to the user's social network contacts as well.

As depicted in FIG. 9A, a user may access the e-wallet system, e.g.,electronic value token transaction processing system 100 or E-WalletAggregator System 1000, via such systems' interactive displaypages/screens (wherein the interactive display pages/screens areaccessed via a user's computer, a user's personal digital assistant orsmart phone, point of sale terminal, kiosk 189, or other device. As FIG.9A depicts, a user may create and/or register an e-wallet or sub-walletby providing certain requested information and agreeing to certain termsand conditions.

As depicted in FIG. 9B, a user may manage its e-wallet by inputtingcertain card specific information into the e-wallet systems interactivedisplay page/screen. In an embodiment, a user may register a gift cardby inputting the gift card's brand, card number, expiration date, CVV2code, and card nickname and selecting the “Add Gift Card to MyWallet”button on the screen.

As shown in FIG. 9C, a user is provided many options for managing ane-wallet and its contents. For example, as shown, a user may review thespecific details associated with the electronic value tokens (depictedas gift cards in FIG. 9C) present in the e-wallet and/or sub-wallet.Moreover, the user could request that the electronic value tokens bepresented as: (i) “Last added” (as shown in FIG. 9C); (ii) as containedin various “Sub-wallets” (sub-wallets could be categorized or nicknamed,such as “Dining,” “Home Improvement,” “Debit,” “Credit,” “Loyalty,”etc.); (iii) as in highest to lowest remaining value; or (iv) as rankedin regards to preference for use.

As is also shown in FIG. 9C, the user has the ability to “Add a GiftCard,” “Add Value,” “Redeem Card,” and “Sell Card.”

The “Add a Gift Card” functionality enables a user to place anelectronic value token into the e-wallet. The “Add a Gift Card”selection provides at least two different methods for the user to add anelectronic value token to the e-wallet. First, an electronic value tokenrepresenting a physical card possessed by the user may be added to thee-wallet. As described in reference to FIG. 9B, by selecting “Add a GiftCard” and the subsequent manner of such addition, the screen display ofFIG. 9B may be presented to the user. Accordingly, the user may add a“gift card” to the e-wallet by inputting the gift card's brand, cardnumber, expiration date, CVV2 code, and card nickname and selecting the“Add Gift Card to MyWallet” button on the screen. Alternatively, theuser may have access to a card reader (e.g., mag stripe reader and/orbar code reader), such as a device attached to a user's computer,personal digital assistant or smart phone, and utilize such device toread information from a physical card, in conjunction with the user'scomputer, personal digital assistant or smart phone, to enter the card'sinformation into the e-wallet system for conversion into an electronicvalue token. Second, an electronic value token representing a physicalcard not already possessed by the user may be added to the e-wallet. Insuch an embodiment, when the user selects this option, the user may bepresented a display screen informing the user of all the different typesand value amounts of electronic value tokens that are available forpurchase. The availability of electronic value tokens for purchase canbe ascribed to the e-wallet system's (e.g., the electronic value tokentransaction processing system's 100) relationships with card issuers,merchants, vendors, and/or processors (e.g., a GiftCard Mall web-basedapplication as provided by BlackHawk Network which provides users withthe ability to select from a variety of different types of gift cards(and varying denominations) and have the cards selected delivered to theuser (or to a user's identified recipient) in either tangible form (viamail or other courier) or delivered electronically (e.g., via theelectronic value token transaction processing system)) or may beascribed to the e-wallet system's (e.g., the electronic value tokentransaction processing system's 100) ability to access an electronicvalue token exchange program 2000, as will be described more fullybelow.

The “Add Value” functionality enables a user to select an electronicvalue token and increase the value of said token. Such “reloading,”“topping off,” or “recharging” of an electronic value token may beperformed as is described in International Application Serial No.PCT/US11/40055, which is incorporated by reference in its entirety. Forexample, when the e-wallet user desires to reload/recharge/top off atelecom-related electronic value token residing in the e-wallet, theuser can select “Add Value” on the display screen which will prompt thesystem to transmit the reload/recharge/top-up request to the electronicvalue token computer 150.

In a first embodiment of the reload/recharge/top-up scenario, theelectronic value token computer 150 approves the request if thetelecom-related electronic value token is activated and associated witha phone number. The electronic value token computer 150 determines thetelecom account associated with the phone number and adds the requestedreload/recharge/top-up amount to the account. The electronic value tokencomputer 150 sends a response to the request (e.g., indicating that thereload/recharge/top-up amount has been added to the associated account).The electronic value token computer 150 transmits areload/recharge/top-up transaction request to the phone number'sassociated telecom carrier. Upon receiving approval of thereload/recharge/top-up transaction request from the telecom carrier, theelectronic value token computer 150 modifies the value of thetelecom-related electronic value token to reflect thereload/recharge/top-up amount. The electronic value token computer 150will cause the display accessed by the user to reflect the modificationof the electronic value token's value, or if the reload/recharge/top-uptransaction request was not approved, the electronic value tokencomputer 150 will cause the display to inform the user as to thatresult. While the “Add Value” functionality has been described inrelation to telecom-related electronic value tokens, the “Add Value”functionality is equally applicable and functionable forreloading/recharging/topping-up electronic value tokens associated withdebit cards, prepaid services cards, gift cards, etc.

The “Redeem Card” functionality enables a user to select an electronicvalue token and use that token to satisfy a purchase, or othertransaction. In the “Redeem Card” scenario, if the whole value of theelectronic value token is not used in the redemption transaction, thesystem will modify/reduce the remaining value of the token and cause thedisplay to inform the user of the “new” reduced value of the token,while also informing all interested parties as to the redemptiontransaction and recording and adjusting any pertinent logs accordingly.Alternatively, when an e-wallet is used in a point of sale-type oftransaction context, rather than the above described e-wallet managementcontext, the “Redeem Card” functionality may be automatically invokedvia transactional information conveyed from a point of sale and thus,the can be based on predetermined rules.

The “Sell Card” functionality enables a user to select an electronicvalue token to monetize via offering the card for sale to (i) anothere-wallet user, (ii) the e-wallet (or sub-wallet) system provider, or(iii) an electronic value token exchange program 2000 (as more fullydescribed herein). In the “Sell Card” scenario, a user will inform thee-wallet system as to the electronic value token it desires to sell,select the forum for such sale from a list of available forums, instructthe system as to how the proceeds from the sale should be remitted tothe e-wallet (e.g., in the form of e-wallet system branded electronicvalue token, value added to other selected electronic value token(s),and/or delivery of a hard/tangible form of receipt that the user maypresent for tender, (e.g., chit, coupon, check, or combination thereof))and, if applicable, instruct the system as to a threshold value for thesale of the electronic value token that the user is not willing to gobelow e.g., set a reserve price. The system will execute the desiredsale transaction, and cause the display to inform the user of theresults of the sale of the electronic value token, while also informingall interested parties as to the sale transaction and recording andadjusting any pertinent logs accordingly.

As is further shown in FIG. 9C, a user may choose to manage “My Rewards”which would bring up a screen showing the user options available due tothe user's receipt of loyalty or other types of rewards for using thee-wallet and/or electronic value tokens. The user may also select“Special Offers” which would bring up a screen showing the user anypromotional-type offerings available to the user via the e-wallet. Theuser may also select “Exchange” which would bring up a screen showingthe user options available for electronic value token exchange via thee-wallet.

In similar fashion as described in reference to the above availablee-wallet management abilities and functionalities, a kiosk 189 may becoupled to the electronic value token transaction computer 150 in atleast one embodiment and function as a user's interface with an e-wallettransaction system to allow the user to access e-wallet managementfunctionalities.

The kiosk 189 may be placed in a high-traffic area such as a shoppingmall, and may perform any electronic wallet management function. Forexample, users may create, delete, and alter their electronic wallets orsub-wallets. Users may also check the balances of electronic valuetokens residing in the e-wallet, add, remove, reload, recharge, print,and exchange value tokens in their electronic wallets or sub-wallets.The kiosk 189 may mirror transactions available through an electronicwallet management website in at least one embodiment, or thefunctionality of an e-wallet enabled personal digital assistant and/orsmart phone. Users may employ a print-on-demand function with theirvalue tokens if a particular retailer does not accept electronic wallettransactions. For example, a user may select a value token to print, anda printer connected to the kiosk 189 will print a physicalrepresentation of the selected value token, for example a receipt havinga scannable bar code linked to the electronic value token. The physicalrepresentation may be a gift card with a magnetic stripe, a paperreceipt or coupon with a barcode or matrix code (e.g., QR code), and thelike. In an embodiment, kiosk 189 may print a physical card, for examplefor an additional printing fee. The user may also provision and/orpartition (e.g., create sub-wallets) an electronic wallet using thekiosk 189. For example, after authentication of the user andidentification of the electronic wallet associated with the user, theuser may insert the user's physical stored value cards into the kiosk189, for example a machine operated kiosk similar to an automatic tellermachine or alternatively a manned kiosk having appropriate card readersand the like. The kiosk 189 may convert the physical stored value cardsinto electronic value tokens in the user's electronic wallet.Afterwards, the physical stored value card may be retained or destroyedby the kiosk 189 or returned to the user. In one embodiment, thephysical stored value card is not usable by the user after theconversion. In another embodiment, the user may have the option to usethe electronic value token or the physical stored value card. In otherwords, both will be “active” and available for use. The user may alsopurchase value tokens to provision a wallet directly from the kiosk 189.

In at least one embodiment, a user is associated with multipleelectronic wallets. In order to identify one wallet out of multiplewallets associated with a user, each of the multiple wallets isassociated with a unique wallet identification (“ID”). A database orlookup table, for example, may be used to access wallet identifications.In at least one embodiment, the wallet ID is customizable by the user.

As referenced with respect to both the primary e-wallet and sub-walletembodiments described above, the disclosed e-wallet and sub-walletmethods and systems provide users with the ability to add value toelectronic value tokens residing in an e-wallet and/or sub-wallet. In anembodiment, similar value-added capabilities and functionalities of theinstantly described electronic value token transaction processing system100 are detailed and described in International Application Serial No.PCT/US11/20570, which is incorporated by reference in its entirety, suchsimilar value-added capabilities and functionalities may be adapted fromthe context described in International Application Serial No.PCT/US11/20570 to be applied in the instant e-wallet/electronic valuetoken context.

Customers may be offered incentives to purchase and/or redeem a valuetoken(s) via value differentiation between the purchase and redemptionvalues of said value token(s).

In an embodiment, a value token with a face value of $25 may bepurchased by a customer for $25, but the electronic value token may beadded to the electronic wallet in the amount of $30—the $25 purchaseprice plus an additional $5 added as an incentive to purchase theelectronic value token. Alternatively, rather than adding cash value tothe electronic value token, the electronic value token may be encodedwith a redemption coupon code for a specific product or service. Forexample, a $15 value token to a coffee house may have an electronicredemption coupon code for a free shot of the customer's syrup of choiceto be added to any coffee purchased at the coffee house. The free shotof syrup may be redeemed in connection with redeeming a portion, or all,of the electronic value token amount or the free shot of syrup may beredeemed separately.

In another embodiment, a value token vendor is able to offer customersincentives to redeem a value token by adding value in addition to thevalue of the electronic value token at the time the customer redeems theelectronic value token. For example, a merchant could run a promotion inwhich it offers customers an additional $5 credit when the customer usesa value token for a purchase at one of the merchant's retail storesduring a specified period of time.

As noted above, the electronic value token transaction computer 150communicates with the datastore 180 and/or the issuers' authorizationsystems 160. The electronic value token transaction computer 150 maycompare one or more of the card identification, the terminalidentification, vendor identification, and the time and date of theactivation request contained within the transaction request to datacontained in the datastore 180 to determine whether the electronic valuetoken to be added/redeemed is eligible for a value added award. Forexample, a vendor may run a promotion to encourage customers to purchasea value token, wherein value tokens purchased within a specified periodof time may be purchased for a price less than the value designated bythe electronic value tokens description or metadata. Thus, a customercould purchase a $25 value token for some amount less than $25, e.g.,$20. In either of the above examples, the value differentiators, e.g.,bonus added to a redemption value of a value token and reduction ofpurchase price for a designated value of a value token, may beapplicable to bundled value token packages and the value differentiatorsdistributed amongst and/or across the electronic value tokens, eitherequally or disproportionately. Similarly, retailers can collaborate forcross-promotions by honoring other retailer's value tokens in full, inpart, or for specific products or promotions. By selecting to use anelectronic wallet at the point of sale, the user may even receive thebenefits of promotions of which the user was unaware. Furthermore, byconfiguring the rules, the user can be assured of getting the bestpromotions at various retailers without comparison shopping. As such,retailers can implement and change promotions at a rapid pace andcross-promote with other retailers on a daily or even hourly basiswithout spending advertising resources to make sure that the user isaware of the promotion and without requiring the user to perform thelegwork involved in traditional redemption models such as cuttingcoupons, inputting various promotional codes, and the like. Moreover,retailers can finely tune promotions to various market segments in orderto strengthen relationships by providing for the segment's particularneeds.

The message modification unit 154 modifies the messages 106 and 110 toadd value added information into the messages. For example, if it isdetermined by the value added determination unit 153 that a value tokento be added is eligible for a value added bonus, the message 106received from the point of sale device 111 is modified by the messagemodification unit 154 to include the determined value added bonus and isthen forwarded as message 109 to the appropriate issuers' authorizationsystem 160 for authorizing the request for the amount specified in theactivation request plus the value added bonus. As another example, if itis determined that the electronic value token is eligible to bepurchased at a discount, the message 106 received from the point of saledevice 111 is modified by the message modification unit 154 (andforwarded as message 109) to indicate to the appropriate issuers'authorization system 160 that the electronic value token will be addedto the electronic wallet for one amount, but that the customer will becharged a lesser amount reflecting the discount associated with theelectronic value token.

In an embodiment, the message modification unit 154 also modifiesmessages 110 from the issuers' authorization systems 160 intended forthe point of sale device 111 to include any information regarding valueadded to the electronic value token that may be printed on the receiptgenerated for the customer as well as information that may be presentedto a cashier on a terminal 101 or 104 that the cashier may communicateto the customer, and such modified messages are forwarded as messages107 to the point of sale device 111.

As referenced with respect to both the primary e-wallet and sub-walletembodiments described above, the disclosed e-wallet and sub-walletmethods and systems provide users with the ability to exchange anelectronic value token residing in the user's e-wallet or sub-walletwith/for an electronic value token not presently residing in the user'se-wallet or sub-wallet, but made available via the e-wallet's orsub-wallet's transaction system(s).

The electronic value token computer's 150 owner and/or operator may earnrevenue via arbitrage-type activities. That is, electronic value tokencomputer's 150 owner and/or operator may keep the difference in goingrates between two electronic value tokens, e.g., a first electronicvalue token being traded/exchanged and a second electronic value tokenbeing desired/obtained. In at least one embodiment, the electronic valuetoken transaction computer 150 may charge the user transaction fee forthe exchange instead. The transaction fee may be flat or based on thesize of the exchange.

The electronic value token transaction computer 150 may also chargeeither or both of the issuers and/or retailers associated with theexchange a flat transaction fee or one based on the amount of theexchange. These fees may be minimal but generated in high volume. Allparties may benefit because the user is receiving value tokens the userwill use in exchange for value tokens the user would not use. Moreover,one issuer and/or retailer is eliminating the debt or inventoryliability associated with the exchanged value token, thus freeing upcapital for other uses. Also, the other issuer and/or retailer may begaining a customer, retaining a loyal customer, or increasing revenue ifthe customer spends more than the amount of the electronic value token.

As referenced with respect to both the primary e-wallet and sub-walletembodiments described above, the disclosed e-wallet and sub-walletmethods and systems provide users with the ability to exchangeelectronic value tokens located in e-wallets and/or sub-wallets forother electronic value tokens not located in said e-wallets orsub-wallets. Such value token exchange may be initiated (1) by ane-wallet user (i) at a point of sale, (ii) at a kiosk, (iii) via auser's personal digital assistant or smart phone, (iv) via web access tothe user's e-wallet, (v) or any other method of accessing the user'se-wallet; or (2) by an application of an e-wallet rule by an e-walletprocessing system, wherein the rule is established by (i) the e-walletuser, (ii) the e-wallet provider, (iii) or a combination thereof.

In at least one embodiment, exchanging a first value token associatedwith a first retailer located in the e-wallet for a second value tokenassociated with a second retailer not located in the e-wallet requiresan exchange rate be applied. This exchange rate may be applied againstthe value of the second value token being sought in the exchange, thusreducing the face value of the second value token is relation to thevalue of the first value token for which it is exchanged or the exchangerate may be applied against some other valued asset located in thee-wallet (as prescribed by any pertinent rules or directives). Theexchange rate may be realized by the e-wallet processing system and/orshared with designated vendors, merchants, and issuers.

The exchange rate may established via an ongoing valuation programoperated by the e-wallet processing system or affiliated entitycomprising the tracking of the use of and interest in electronic valuetokens, gift cards (or other similar instruments), the acquisition ofsuch electronic value tokens, gift cards (or other similar instruments)from other e-wallet users or other sources, and the establishment ofdynamically varying values for all such electronic value tokens and giftcard-type instruments available to the e-wallet processing system forincorporation into an electronic value token exchange program.

The above-described electronic value token exchange program may beexemplified by the following discussion. An e-wallet user can approachan e-wallet associated kiosk 189 at Retailer A's establishment. Thee-wallet user interfaces with the kiosk 189 and provides the kiosk withe-wallet identifying information (e.g., as described in Table 1 herein“accountid”). The provision of identifying information may be made viamanual input by the kiosk's user or may be made automatically viacommunication between the e-wallet user's personal digital assistant (orproxy card 200) and the kiosk 189. The e-wallet user may then use thekiosk 189 to access the e-wallet's electronic value token exchangeprogram and the kiosk 189 may be further used to facilitate and completeany requested electronic value token exchange. In an embodiment, thee-wallet user may wish to exchange an electronic value token issuedand/or accepted by Retailer B contained in the user's e-wallet (or asub-wallet thereof) for an electronic value token issued and/or acceptedby Retailer A. The e-wallet user interfacing with kiosk 189 can resultin the e-wallet user being presented with a screen display such as isdepicted in FIG. 9C. Besides providing the e-wallet user with theability to review the contents of the e-wallet, the display allows thee-wallet user to select an “Exchange” tab from the availablefunctionalities. The “Exchange” tab will then present the e-wallet userwith the options available for electronic value token exchange. Asdepicted in FIG. 9D, such options can comprise: (1) view a selection ofelectronic value token(s) available for acquisition; (2) view theselection of electronic value token(s) presently residing in e-wallet;(3) view the various exchange rates for the identified electronic valuetoken(s) for acquisition as calculated in view of the electronic valuetokens selected for removal (exchange) from the e-wallet (exchange ratesmay vary based on types/retailers of electronic value tokens selectedfor exchange); (4) view options for satisfying exchange rate (e.g., (i)reduction in value of electronic value token selected for acquisition tomeet the exchange rate or (ii) application of the amount of the exchangerate to some other asset residing in the e-wallet such as a credit cardvalue token or a debit card value token); (5) view a selection ofoptions for delivery of the electronic value token selected foracquisition such as (i) delivery into the e-wallet (or sub-wallet), (ii)delivery via email, SMS, social media, or other electronic method to apersonal digital assistant or computer, (iii) print out of a tangibleversion of the electronic value token (e.g., via print on receipt-typecapability as described in U.S. patent application Ser. No. 12/719,741which is incorporated by reference in its entirety) at the kiosk orother user-selected print device. The user may make its desiredselections in response to the information provided in each of theabove-describe screens, as each of the described screen view optionsinclude functionality allowing for selection of the displayed options.In this example, the user selects that the Retailer B $25.00 electronicvalue token residing in the e-wallet is to be exchanged for a Retailer Aelectronic value token. As a result, the electronic value token exchangeprogram prompts the kiosk 189 to display that the requested exchangewill result in the user acquiring a Retailer A electronic value token inthe amount of $24.75 if the user selects that the exchange rate beapplied against the value of the Retailer A electronic value token (theexchange rate will vary from transaction to transaction, the exchangerate could be any value, e.g., $0.001 to $10.00, or any values below,within, or above this range). The user makes such selection. Theelectronic value token exchange program prompts the kiosk 189 to displaythe available delivery methods and the user selects delivery into thee-wallet. The electronic value token exchange program prompts the kiosk189 to display another screen similar to FIG. 9C, but indicating thatthe e-wallet now contains a Retailer A electronic value token in theamount of $24.75.

As a result of the above “Exchange” transaction, the e-wallet userreceived its desired Retailer A electronic value token and theelectronic value token exchange program received a Retailer B $25.00electronic value token. As part of the above-described transaction, theelectronic value token exchange program contacted the electronic valuetoken issuing entity of Retailer A electronic value tokens (e.g., in anembodiment issuing entity of Retailer A electronic value tokens could bethe electronic value token exchange program 2000) and requested aRetailer A $24.75 electronic value token be provided to meet thee-wallet user's request; alternatively, the electronic value tokenexchange program modified a Retailer A electronic value token it alreadycontrolled, e.g., modified a Retailer A $25.00 electronic value token toonly be worth $24.75 and informed the issuing entity of Retailer Aelectronic value tokens that it could reduce its liability associatedwith said card by $0.25. Further, the electronic value token exchangeprogram 2000 will contact the Retailer B electronic value token issuerand provide the issuer with the appropriate Retailer B $25.00 electronicvalue token identification so that the issuer can remove that Retailer B$25.00 electronic value token from its list of liabilities. Thus, as anend result, the electronic value token exchange program's activitieshave resulted in a $0.25 value (the exchange rate, i.e., difference invalue of electronic value token acquired by requesting user andelectronic value token surrendered by requesting user as part of theexchange) that may be allocated to interested parties per establishedcontractual obligations.

In an alternative scenario, if the e-wallet requesting user selects theexchange rate to be satisfied by another asset residing in the e-walletor sub-wallet, such as a credit card electronic value token or a debitcard electronic value token, the e-wallet user would be provided with a$25.00 Retailer A electronic value token matching the $25.00 Retailer Aelectronic value token surrendered in the transaction and the exchangerate of $0.25 would be realized from charging against the credit cardelectronic value token or debiting against the debit card electronicvalue token. Such actions would be transacted with communicationsbetween the electronic value token exchange program and the credit cardelectronic value token or the debit card electronic value tokenrequesting that the $0.25 exchange rate value be paid to the electronicvalue token exchange program. Thus, again as an end result, theelectronic value token exchange program's activities would have resultedin a $0.25 value (the exchange rate) that may be allocated to interestedparties per established contractual obligations.

The above-described electronic value token exchange transaction (or anydescribed variation thereof), although described in the kiosk 189context, could also be performed at point of sale, via a personaldigital assistant with e-wallet functionality, or via a computer withaccess the user's e-wallet.

In an alternative electronic value token exchange embodiment, asdiscussed previously, the e-wallet may automatically direct electronicvalue token exchange activities. For example, the e-wallet user maymanage the e-wallet so that upon the occasion when the user presents thee-wallet to satisfy a transaction at retail establishment, e.g.,Retailer Q, and the e-wallet contains no Retailer Q branded electronicvalue tokens, the e-wallet will automatically, and in real time,initiate an electronic value token exchange process wherein the e-walletcommunicates a request for electronic value token exchange to theelectronic value token transaction computer 150. In this example, thee-wallet user has managed the e-wallet so that all electronic valuetokens associated with prepaid services (gift card-type electronic valuetokens) are located in a designated sub-wallet and each of saidelectronic value tokens were placed/ordered/designated in the sub-walletvia a preferential ranking system, e.g., most preferred electronic valuetoken or token type (e.g., #1) to least preferred electronic value tokenor token type (e.g., #22, if there are 22 types of electronic valuetokens in the sub-wallet. For example, Retailer M branded electronicvalue tokens may be designated as most preferred and Retailer L brandedelectronic value tokens may be designated as least preferred. Further inthe example, the e-wallet also has been provided with rules by the userthat directs the e-wallet, in circumstances wherein the e-wallet hasbeen presented to facilitate a transaction at a retailer in which thee-wallet contains none of said retailer's electronic value tokens (thee-wallet will recognize the retailer based on information exchangedbetween the e-wallet and the retailer's communication devices at theonset of the original transaction), such as the Retailer Q scenariodescribed above, the e-wallet rules direct the e-wallet to initiate anelectronic value token exchange request and to include in said requestthe exchange of the least preferred electronic value token residing inthe e-wallet, i.e., the Retailer L branded electronic value token (#22)and if necessary preferred electronic value token #21, #20, etc., for aRetailer Q electronic value token in an amount sufficient to meet theoriginal transaction's amount. The electronic value token transactioncomputer 150, upon receipt of the electronic value token exchangerequest, communicates with an electronic value token exchange program2000, e.g., an electronic value token distributor, (which is part of theoverall electronic value token transaction processing system 100) toeffectuate the requested electronic value token exchange. The requestedelectronic value token exchange is performed, the e-wallet receives therequested Retailer Q branded electronic value token, which iscoincidentally used in conducting the original transaction, and thee-wallet surrenders (or makes unavailable for use and only available formodification) the Retailer L branded electronic value token to theelectronic value token transaction computer 150, which in this case wasactually valued in excess of the requested Retailer Q branded electronicvalue token. As such, the electronic value token transaction computer150, modifies the value of the Retailer L branded electronic value token(either internally or via communication with the Retailer L brandedelectronic value token's issuing system) to reflect the value reductionbased on the provided Retailer Q branded electronic value token,extracts the exchange rate for the exchange of the Retailer Q brandedelectronic value token for the Retailer L branded electronic value token(as will be discussed more fully herein), communicates the transactionalinformation to all interested parties, and returns (or makes availableagain) the value-modified Retailer L branded value token to the user'se-wallet.

In an alternate embodiment, the e-wallet's electronic value tokenexchange rules could have provided that the e-wallet query theelectronic value token transaction computer 150 regarding the bestavailable exchange rate for the electronic value tokens residing in thee-wallet and make the exchange based on the best exchange rate ratherthan the ranking of the electronic value tokens. Further the e-walletuser may subjectively determine which electronic token(s) should beexchanged to satisfy a transaction.

In an embodiment, the electronic token exchange program 2000 may surveya user's e-wallets and sub-wallets maintained by the electronic valuetoken transaction computer 150 and make the e-wallet user an offer(s)for electronic value token exchange(s). For example, the electronictoken exchange program 2000, as part of the survey may determine, basedon (i) the history of the e-wallet's use; (ii) the length of time anunused electronic value token has resided in an e-wallet; (iii) thedemand for certain electronic value tokens in the marketplace; (iv)dates for spoilage of electronic value tokens; (v) promotional offersfor acquiring electronic value tokens; and (vi) combinations thereof, tooffer an e-wallet user to exchange an electronic value token(s)presently residing in the user's e-wallet/sub-wallet for an electronicvalue token(s) not presently residing in the user's e-wallet/sub-wallet.In an embodiment, the electronic token exchange program 2000 maysupplement the offer for exchange with a value added/bonus incentive asdescribed previously herein. In another embodiment, the offer mayinclude an option for the user to place a portion of the exchange valueamount into a savings wallet, as will be more fully below.

As referenced with respect to both the primary e-wallet and sub-walletembodiments described above, the disclosed e-wallet and sub-walletmethods and systems provide users with the ability to designate thelocations of value tokens residing in an e-wallet or sub-wallet, as wellas rules prescribing the use and/or availability of said e-wallet and/orsub-wallet. As also described herein, electronic value token(s) may beremoved from a sub-wallet configured to allow redemption activities(hereinafter “fully-redeemable” designated e-wallet or sub-wallet) andplaced into a sub-wallet configured for savings activities with limitedredemption possibilities (hereinafter “savings” designated e-wallet orsub-wallet). In fact, the instant system provides for electronic valuetoken(s) to be placed into a “savings” designated e-wallet or sub-walletat the time the electronic value token is made available to the e-walletor sub-wallet.

In an embodiment, electronic value tokens may be designated for and/orplaced in certain e-wallets and/or sub-wallets which have rulesproviding that the e-wallets or sub-wallets are to be used for savingsactivities and thus are not readily available for general access or forredemption/exchange activities. In an embodiment, similar savingscapabilities, functionalities, requirements, and limitations of theinstantly described electronic value token transaction processing system100 are detailed and described in International Application Serial No.PCT/US11/49338 which is incorporated by reference in its entirety, suchsimilar savings capabilities, functionalities, requirements, andlimitations may be adapted from the context described in InternationalApplication Serial No. PCT/US11/49338 to be applied in the instante-wallet/electronic value token context.

At least in some embodiments, allows a user to easily redistributeelectronic value tokens (e.g., debit card-related electronic valuetokens) from a “fully-redeemable” designated e-wallet or sub-wallet to a“savings” designated e-wallet or sub-wallet, and vice versa. The usermay be limited by law to a given number of, e.g., six, transfers out ofthe “savings” designated e-wallet or sub-wallet to the“fully-redeemable” designated e-wallet or sub-wallet per calendar month.The user may designate one-time transfers through the e-wallet system'swebsite, WR, personal digital assistant or smart phone, or with acustomer service representative. The user may also establish andautomated transfers between the “fully-redeemable” designated e-walletor sub-wallet and the “savings” designated e-wallet or sub-wallet. Toencourage savings, users may be presented with option to automaticallyfund the “savings” designated e-wallet or sub-wallet from the“fully-redeemable” designated e-wallet or sub-wallet that may betriggered by various transaction events, including: (a) upon receiving adirect deposit, (b) when a reload/recharge/topping up transactionoccurs, and/or (c) at a designated time interval (e.g., recurring weeklyor monthly). The user can elect all, some, or none of the optionsavailable. Moreover, the above events may be transacted regardless ofthe “fully-redeemable” designated or “savings” designated e-wallet orsub-wallet's current balance. The user may have the ability to select anamount or percent of electronic value tokens loaded onto“fully-redeemable” designated e-wallet or sub-wallet. Where the userchooses a time interval for automatic transfers, the user may be able toselect a preferred date. The user would have the flexibility to update,edit, or otherwise change the automatic funding option at any time. Anynegative “fully-redeemable” designated e-wallet or sub-wallet may needto be cured prior to initiating any automatic or one-time transfers to“savings” designated e-wallet or sub-wallet. If an automatic transfercannot be fully funded or cannot be funded at all, any amounts availablewill be taken from the “fully-redeemable” designated e-wallet orsub-wallet to the “savings” designated e-wallet or sub-wallet and anotification will be provided to the e-wallet user describing thetransaction. Automatic transfers will continue thereafter for thedesignated transfer option and amount.

The electronic value token transaction computer 150 above may beimplemented on any particular machine with sufficient processing power,memory resources, and network throughput capability to handle thenecessary workload placed upon it.

All of, or a portion of, the system described above may be implementedon any particular machine, or machines, with sufficient processingpower, memory resources, and throughput capability to handle thenecessary workload placed upon the computer, or computers. FIG. 8illustrates a computer system 580 suitable for implementing all, or aportion of, one or more embodiments disclosed herein. The computersystem 580 includes a processor 582 (which may be referred to as acentral processor unit or CPU) that is in communication with memorydevices including secondary storage 584, read only memory (ROM) 586,random access memory (RAM) 588, input/output (I/O) devices 590, andnetwork connectivity devices 592. The processor 582 may be implementedas one or more CPU chips.

It is understood that by programming and/or loading executableinstructions onto the computer system 580, at least one of the CPU 582,the RAM 588, and the ROM 586 are changed, transforming the computersystem 580 in part into a particular machine or apparatus having thenovel functionality taught by the present disclosure. It is fundamentalto the electrical engineering and software engineering arts thatfunctionality that can be implemented by loading executable softwareinto a computer can be converted to a hardware implementation by wellknown design rules. Decisions between implementing a concept in softwareversus hardware typically hinge on considerations of stability of thedesign and numbers of units to be produced rather than any issuesinvolved in translating from the software domain to the hardware domain.Generally, a design that is still subject to frequent change may bepreferred to be implemented in software, because re-spinning a hardwareimplementation is more expensive than re-spinning a software design.Generally, a design that is stable that will be produced in large volumemay be preferred to be implemented in hardware, for example in anapplication specific integrated circuit (ASIC), because for largeproduction runs the hardware implementation may be less expensive thanthe software implementation. Often a design may be developed and testedin a software form and later transformed, by well known design rules, toan equivalent hardware implementation in an application specificintegrated circuit that hardwires the instructions of the software. Inthe same manner as a machine controlled by a new ASIC is a particularmachine or apparatus, likewise a computer that has been programmedand/or loaded with executable instructions may be viewed as a particularmachine or apparatus.

The secondary storage 584 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 588 is not large enough tohold all working data. Secondary storage 584 may be used to storeprograms which are loaded into RAM 588 when such programs are selectedfor execution. The ROM 586 is used to store instructions and perhapsdata which are read during program execution. ROM 586 is a non-volatilememory device which typically has a small memory capacity relative tothe larger memory capacity of secondary storage 584. The RAM 588 is usedto store volatile data and perhaps to store instructions. Access to bothROM 586 and RAM 588 is typically faster than to secondary storage 584.The secondary storage 584, the RAM 588, and/or the ROM 586 may bereferred to in some contexts as computer readable storage media and/ornon-transitory computer readable media.

I/O devices 590 may include printers, video monitors, liquid crystaldisplays (LCDs), touch screen displays, keyboards, keypads, switches,dials, mice, track balls, voice recognizers, card readers, paper tapereaders, or other well-known input devices.

The network connectivity devices 592 may take the form of modems, modembanks, Ethernet cards, universal serial bus (USB) interface cards,serial interfaces, token ring cards, fiber distributed data interface(FDDI) cards, wireless local area network (WLAN) cards, radiotransceiver cards such as code division multiple access (CDMA), globalsystem for mobile communications (GSM), long-term evolution (LTE),worldwide interoperability for microwave access (WiMAX), and/or otherair interface protocol radio transceiver cards, and other well-knownnetwork devices. These network connectivity devices 592 may enable theprocessor 582 to communicate with the Internet or one or more intranets.With such a network connection, it is contemplated that the processor582 might receive information from the network, or might outputinformation to the network in the course of performing theabove-described method steps. Such information, which is oftenrepresented as a sequence of instructions to be executed using processor582, may be received from and outputted to the network, for example, inthe form of a computer data signal embodied in a carrier wave.

Such information, which may include data or instructions to be executedusing processor 582 for example, may be received from and outputted tothe network, for example, in the form of a computer data baseband signalor signal embodied in a carrier wave. The baseband signal or signalembedded in the carrier wave, or other types of signals currently usedor hereafter developed, may be generated according to several methodswell known to one skilled in the art. The baseband signal and/or signalembedded in the carrier wave may be referred to in some contexts as atransitory signal.

The processor 582 executes instructions, codes, computer programs,scripts which it accesses from hard disk, floppy disk, optical disk(these various disk based systems may all be considered secondarystorage 584), ROM 586, RAM 588, or the network connectivity devices 592.While only one processor 582 is shown, multiple processors may bepresent. Thus, while instructions may be discussed as executed by aprocessor, the instructions may be executed simultaneously, serially, orotherwise executed by one or multiple processors. Instructions, codes,computer programs, scripts, and/or data that may be accessed from thesecondary storage 584, for example, hard drives, floppy disks, opticaldisks, and/or other device, the ROM 586, and/or the RAM 588 may bereferred to in some contexts as non-transitory instructions and/ornon-transitory information.

In an embodiment, the computer system 580 may comprise two or morecomputers in communication with each other that collaborate to perform atask. For example, but not by way of limitation, an application may bepartitioned in such a way as to permit concurrent and/or parallelprocessing of the instructions of the application. Alternatively, thedata processed by the application may be partitioned in such a way as topermit concurrent and/or parallel processing of different portions of adata set by the two or more computers. In an embodiment, virtualizationsoftware may be employed by the computer system 580 to provide thefunctionality of a number of servers that is not directly bound to thenumber of computers in the computer system 580. For example,virtualization software may provide twenty virtual servers on fourphysical computers. In an embodiment, the functionality disclosed abovemay be provided by executing the application and/or applications in acloud computing environment. Cloud computing may comprise providingcomputing services via a network connection using dynamically scalablecomputing resources. Cloud computing may be supported, at least in part,by virtualization software. A cloud computing environment may beestablished by an enterprise and/or may be hired on an as-needed basisfrom a third party provider. Some cloud computing environments maycomprise cloud computing resources owned and operated by the enterpriseas well as cloud computing resources hired and/or leased from a thirdparty provider.

In an embodiment, some or all of the functionality disclosed above maybe provided as a computer program product. The computer program productmay comprise one or more computer readable storage medium havingcomputer usable program code embodied therein to implement thefunctionality disclosed above. The computer program product may comprisedata structures, executable instructions, and other computer usableprogram code. The computer program product may be embodied in removablecomputer storage media and/or non-removable computer storage media. Theremovable computer readable storage medium may comprise, withoutlimitation, a paper tape, a magnetic tape, magnetic disk, an opticaldisk, a solid state memory chip, for example analog magnetic tape,compact disk read only memory (CD-ROM) disks, floppy disks, jump drives,digital cards, multimedia cards, and others. The computer programproduct may be suitable for loading, by the computer system 580, atleast portions of the contents of the computer program product to thesecondary storage 584, to the ROM 586, to the RAM 588, and/or to othernon-volatile memory and volatile memory of the computer system 580. Theprocessor 582 may process the executable instructions and/or datastructures in part by directly accessing the computer program product,for example by reading from a CD-ROM disk inserted into a disk driveperipheral of the computer system 580. Alternatively, the processor 582may process the executable instructions and/or data structures byremotely accessing the computer program product, for example bydownloading the executable instructions and/or data structures from aremote server through the network connectivity devices 592. The computerprogram product may comprise instructions that promote the loadingand/or copying of data, data structures, files, and/or executableinstructions to the secondary storage 584, to the ROM 586, to the RAM588, and/or to other non-volatile memory and volatile memory of thecomputer system 580.

In some contexts, the secondary storage 584, the ROM 586, and the RAM588 may be referred to as a non-transitory computer readable medium or acomputer readable storage media. A dynamic RAM embodiment of the RAM588, likewise, may be referred to as a non-transitory computer readablemedium in that while the dynamic RAM receives electrical power and isoperated in accordance with its design, for example during a period oftime during which the computer 580 is turned on and operational, thedynamic RAM stores information that is written to it. Similarly, theprocessor 582 may comprise an internal RAM, an internal ROM, a cachememory, and/or other internal non-transitory storage blocks, sections,or components that may be referred to in some contexts as non-transitorycomputer readable media or computer readable storage media.

The ordering of steps in the various processes, data flows, andflowcharts presented are for illustration purposes and do notnecessarily reflect the order that various steps must be performed. Thesteps may be rearranged in different orders in different embodiments toreflect the needs, desires and preferences of the entity implementingthe systems. Furthermore, many steps may be performed simultaneouslywith other steps in some embodiments.

Also, techniques, systems, subsystems and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as directly coupled or communicating witheach other may be coupled through some interface or device, such thatthe items may no longer be considered directly coupled to each other butmay still be indirectly coupled and in communication, whetherelectrically, mechanically, or otherwise with one another. Otherexamples of changes, substitutions, and alterations are ascertainable byone skilled in the art and could be made without departing from thespirit and scope disclosed. The following numbered entries represent anon-exhaustive collection of exemplary embodiments of the instantlydisclosed subject matter:

1. A computer implemented method, comprising:

receiving a request to process a payment transaction against anelectronic wallet;

identifying authentication information of the request;

identifying a value token in the electronic wallet; and

applying at least a portion of the value token to at least a portion ofthe request.

2. The method of 1, further comprising:

accepting an authentication token to access the electronic wallet.

3. The method of 2, wherein the authentication information is based onthe authentication token, wherein the authentication token comprises aproxy card, a mobile device, a password, a biometric identifier, orcombinations thereof.

4. The method of 1, wherein the electronic wallet comprises a primarywallet and a sub-wallet.

5. The method of 4, further comprising:

processing at least a portion of the request via the primary wallet.

6. The method of 4, further comprising:

processing at least a portion of the request via the sub-wallet.

7. The method of 4, wherein the primary wallet comprises the valuetoken, the method further comprising:

determining the request is related to the primary wallet; and

determining the value token is capable of meeting the request.

8. The method of 7, wherein applying at least a portion of the valuetoken comprises applying at least a portion of the value token of theprimary wallet to the request.

9. The method of 4, wherein the sub-wallet comprises the value token,the method further comprising:

determining the request is related to the sub-wallet; and

determining the value token is capable of meeting the request.

10. The method of 9, wherein applying at least a portion of the valuetoken comprises applying at least a portion of the value token of thesub-wallet to the request.

11. The method of 4, wherein the electronic wallet comprises two or morevalue tokens, wherein the primary wallet comprises at least one of thetwo or more value tokens, wherein the sub-wallet comprises at leastanother of the two or more value tokens.

12. The method of 11, further comprising:

determining a portion of the request is related to the primary wallet;and

determining another portion of the request is related to the sub-wallet.

13. The method of 12, further comprising:

applying at least a portion of the primary wallet's value token to therequest; and

applying at least a portion of the sub-wallet's value token to therequest.

14. The method of 8 or 13, wherein the value token of the primary walletis applied to the request under a rule of the primary wallet or therequest.

15. The method of 10 or 13, wherein the value token of the sub-wallet isapplied to the request under a rule of the sub-wallet or the request.

16. The method of 4, wherein an aggregator system receives the request,the method further comprising:

determining at least a portion of the request may be processed in thesub-wallet; and

sending the portion of the request from the aggregator system to a thirdparty.

17. The method of 1, wherein the request includes an identity of a pointof sale terminal; authentication information; an amount of a purchase;an identity of the value token issuer; an identity of a vendor; anidentity of a location; a time of the request; a date of the request;information identifying a primary wallet, sub-wallet, or a combinationthereof; transaction data; authentication data; or combinations thereof.

18. The method of 1, wherein the value token comprises an electronicrepresentation of value, wherein the electronic representation of valuecomprises a credit card, debit card, gift card, prepaid telephone card,loyalty card, membership card, ticket or ticket card, entertainmentcard, sports card, prepaid card, coupon, admission pass, prepaid orpre-purchases of goods or services, cash, currency, credit card account,debit card account, merchant account, bank account, merchant-issuedcredit, merchant-issued point, merchant-issued promotional value,merchant-accepted credit, merchant-accepted point, merchant-acceptedpromotional value, or combinations thereof.

19. The method of 18, wherein the value token further comprises at leasttwo electronic representations of value of different types.

20. The method of 1, wherein the value token comprises a closed loopaccount number, wherein applying at least a portion of the value tokencomprises crediting or debiting a closed loop account associated withthe closed loop account number.

21. The method of 1, wherein the value token comprises an open loopaccount number, wherein applying at least a portion of the value tokencomprises crediting or debiting an open loop account associated with theopen loop account number.

22. The method of 1, wherein applying at least a portion of the valuetoken comprises using the value token according to a set of configurablerules specifying priority of the value tokens.

23. The method of 22, wherein the priority is based on a transactioninformation variable comprising physical location of a retaileroriginating the electronic wallet request; transaction amount; type ofretailer; time of day; day of week; week of month; month of year;department of retailer originating the electronic wallet request; laneof retailer originating the electronic wallet request; identification ofchecker; parent company of a retailer originating the electronic walletrequest; value of value tokens; type of the electronic wallet request;or combinations thereof.

24. The method of 1, wherein applying at least a portion of the valuetoken comprises using the value token according to a set of configurablerules specifying percentages of the electronic wallet request to whichvalue tokens may be applied.

25. The method of 1, further comprising:

examining a rule associated with the electronic wallet.

26. The method of 25, wherein examining a rule comprises:

examining a priority of the value token.

27. The method of 25, wherein examining a rule comprises:

examining a percentage of the request;

wherein applying at least a portion of the value token comprisesapplying at least a portion of the value token to the request accordingto the percentage.

28. The method of 1, wherein the electronic wallet comprises a closedloop-related value token and an open loop-related value token, themethod further comprising:

selecting the closed loop-related value token; and

then selecting the open loop-related value token.

29. The method of 1, wherein the electronic wallet comprises an openloop-related value token, the method further comprising:

withholding the open loop-related value token from being applied to therequest.

30. The method of 1, further comprising:

exchanging at least a portion of the value token of the electronicwallet for at least a portion of a second value token not located in theelectronic wallet.

31. The method of 30, further comprising:

applying an exchange rate against the second value token or an assetlocated in the electronic wallet.

32. The method of 30, wherein exchanging at least a portion of the valuetoken comprises:

contacting a second value token distributor; and

requesting the second value token distributor to provide the secondvalue token.

33. The method of 1, wherein the electronic wallet comprises a firstsub-wallet and a second sub-wallet, wherein the first sub-walletcomprises the value token, the method further comprising:

placing the value token of the first sub-wallet into the secondsub-wallet.

34. The method of 1, further comprising:

provisioning the electronic wallet with the value token.

35. The method of 34, wherein the value token is provisioned in anamount different than the purchase price.

36. The method of 34, wherein provisioning the electronic walletcomprises encoding the value token with a coupon code.

37. The method of 34, wherein provisioning the electronic walletcomprises adding the value token to the electronic wallet.

38. The method of 1, wherein the electronic wallet comprises asavings-designated sub-wallet, the method further comprising:

placing at least a portion of the value token in the savings-designatedsub-wallet.

39. A computer implemented method, comprising:

receiving a request to process a payment transaction against anelectronic wallet;

determining the request contains valid authentication information;

determining a value token, or a combination of value tokens, associatedwith the electronic wallet is capable of meeting the request; and

applying at least a portion of the value token to at least a portion ofthe request.

40. The method of 39, further comprising:

accepting an authentication token to access the electronic wallet.

41. The method of 40, wherein the authentication information is based onthe authentication token, wherein the authentication token comprises aproxy card, a mobile device, a password, a biometric identifier, orcombinations thereof.

42. The method of 39, wherein the electronic wallet comprises a primarywallet and a sub-wallet.

43. The method of 42, further comprising:

processing at least a portion of the request via the primary wallet.

44. The method of 43, further comprising:

processing at least another portion of the request via the sub-wallet.

45. The method of 42, wherein the primary wallet comprises the valuetoken, the method further comprising:

determining the request is related to the primary wallet;

wherein applying at least a portion of the value token comprisesapplying at least a portion of the value token of the primary wallet tothe request.

46. The method of 42, wherein the sub-wallet comprises the value token,the method further comprising:

determining the request is related to the sub-wallet;

wherein applying at least a portion of the value token comprisesapplying at least a portion of the value token of the sub-wallet to therequest.

47. The method of 42, wherein the electronic wallet comprises two ormore value tokens, wherein the primary wallet comprises at least one ofthe two or more value tokens, wherein the sub-wallet comprises at leastanother of the two or more value tokens.

48. The method of 47, further comprising:

determining a portion of the request is related to the primary wallet;and

determining another portion of the request is related to the sub-wallet.

49. The method of 48, further comprising:

applying at least a portion of the primary wallet's value token to therequest; and

applying at least a portion of the sub-wallet's value token to therequest.

50. The method of 45 or 49, wherein the value token of the primarywallet is applied to the request under a rule of the primary wallet orthe request.

51. The method of 46 or 49, wherein the value token of the sub-wallet isapplied to the request under a rule of the sub-wallet or the request.

52. The method of 42, wherein an aggregator system receives the request,the method further comprising:

determining at least a portion of the request may be processed in thesub-wallet; and

sending the portion of the request from the aggregator system to a thirdparty.

53. A method for a sub-wallet in an electronic wallet system, the methodcomprising:

receiving a request to process a payment transaction against anelectronic wallet from a provider of a primary wallet;

determining a value token is capable of meeting the request; and

applying at least a portion of the value token to at least a portion ofthe request.

54. The method of 53, further comprising:

determining the request is related to the sub-wallet;

wherein applying at least a portion of the value token comprisesapplying at least a portion of the value token of the sub-wallet to therequest.

55. The method of 53, wherein the sub-wallet comprises a sub-sub-wallet.

56. The method of 55, further comprising:

determining the request is related to the sub-sub-wallet;

wherein applying at least a portion of the value token comprisesapplying the value token of the sub-sub-wallet to the request.

57. The method of 55, further comprising:

determining a portion of the request is related to the sub-wallet; and

determining another portion of the request is related to thesub-sub-wallet.

58. The method of 55, wherein the sub-wallet comprises two or more valuetokens, wherein the sub-wallet comprises at least one of the two or morevalue tokens, wherein the sub-sub-wallet comprises at least another ofthe two or more value tokens.

59. The method of 58, further comprising:

applying at least a portion of the sub-wallet's value token to therequest; and

applying at least a portion of the sub-sub-wallet's value token to therequest.

60. The method of 54 or 59, wherein the value token of the sub-wallet isapplied to the request under a rule of the sub-wallet or the request.

61. The method of 56 or 59, wherein the value token of thesub-sub-wallet is applied to the request under a rule of thesub-sub-wallet or the request.

62. A method for managing the contents of an electronic wallet,comprising:

receiving a request related to an electronic wallet, wherein the requestcomprises an electronic wallet request, a balance inquiry request, aregistration request, an activation request, a redemption request, orcombinations thereof; and

managing the contents of the electronic wallet according to the request.

63. The method of 62, wherein managing the contents comprises:

exchanging at least a portion of a value token of the electronic walletfor at least a portion of a second value token not located in theelectronic wallet.

64. The method of 63, further comprising:

applying an exchange rate against the second value token or an assetlocated in the electronic wallet.

65. The method of 63, wherein exchanging at least a portion of the valuetoken comprises:

contacting a second value token distributor of the second value token;and

requesting the second value token distributor to provide the secondvalue token.

66. The method of 62, wherein the electronic wallet comprises a firstsub-wallet and a second sub-wallet, wherein the first sub-walletcomprises a value token, the method further comprising:

placing the value token of the first sub-wallet into the secondsub-wallet.

67. The method of 62, further comprising:

provisioning the electronic wallet with a value token.

68. The method of 67, wherein provisioning the electronic walletcomprises adding the value token to the electronic wallet.

69. The method of 67, wherein the value token is provisioned in anamount different than the purchase price.

70. The method of 67, wherein provisioning the electronic walletcomprises encoding the value token with a coupon code.

71. The method of 62, wherein the electronic wallet comprises asavings-designated sub-wallet, the method further comprising:

placing at least a portion of a value token in the savings-designatedsub-wallet.

72. A non-transitory machine-readable storage medium comprisingexecutable instructions that, when executed, cause one or moreprocessors to:

receive a request to process a payment transaction against an electronicwallet;

identify authentication information of the request;

identify a value token in the electronic wallet; and

apply at least a portion of the value token to at least a portion of therequest.

73. A non-transitory machine-readable storage medium comprisingexecutable instructions that, when executed, cause one or moreprocessors to:

-   -   receive a request to process a payment transaction against an        electronic wallet;

determine the request contains valid authentication information;

determine a value token, or a combination of value tokens, associatedwith the electronic wallet is capable of meeting the request; and

apply at least a portion of the value token to at least a portion of therequest.

74. A non-transitory machine-readable storage medium comprisingexecutable instructions that, when executed, cause one or moreprocessors to:

receive a request to process a payment transaction against an electronicwallet from a provider of a primary wallet;

determine a value token is capable of meeting the request; and

apply at least a portion of the value token to at least a portion of therequest.

75. A non-transitory machine-readable storage medium comprisingexecutable instructions that, when executed, cause one or moreprocessors to:

receive a request related to an electronic wallet, wherein the requestcomprises an electronic wallet request, a balance inquiry request, aregistration request, an activation request, a redemption request, orcombinations thereof; and

manage the contents of the electronic wallet according to the request.

76. A system comprising:

one or more processors;

a memory coupled to at least one of the one or more processors;

the memory comprising executable instructions that, when executed, causethe one or more processors to:

receive a request to process a payment transaction against an electronicwallet;

identify authentication information of the request;

identify a value token in the electronic wallet; and

apply at least a portion of the value token to at least a portion of therequest.

77. The system of 76, wherein the one or more processors are furthercaused to accept an authentication token to access the electronicwallet.

78. The system of 77, wherein the authentication information is based onthe authentication token, wherein the authentication token comprises aproxy card, a mobile device, a password, a biometric identifier, orcombinations thereof.

79. The system of 76, wherein the electronic wallet comprises a primarywallet and a sub-wallet.

80. The system of 79, wherein the one or more processors are furthercaused to process at least a portion of the request via the primarywallet.

81. The system of 79, wherein the one or more processors are furthercaused to process at least a portion of the request via the sub-wallet.

82. The system of 79, wherein the primary wallet comprises the valuetoken, wherein the one or more processors are further caused to:

determine the request is related to the primary wallet; and

determine the value token is capable of meeting the request.

83. The system of 82, wherein apply at least a portion of the valuetoken comprises apply at least a portion of the value token of theprimary wallet to the request.

84. The system of 79, wherein the sub-wallet comprises the value token,wherein the one or more processors are further caused to:

determine the request is related to the sub-wallet; and

determine the value token is capable of meeting the request.

85. The system of 84, wherein apply at least a portion of the valuetoken comprises apply at least a portion of the value token of thesub-wallet to the request.

86. The system of 79, wherein the electronic wallet comprises two ormore value tokens, wherein the primary wallet comprises at least one ofthe two or more value tokens, wherein the sub-wallet comprises at leastanother of the two or more value tokens.

87. The system of 86, wherein the one or more processors are furthercaused to:

determine a portion of the request is related to the primary wallet; and

determine another portion of the request is related to the sub-wallet.

88. The system of 87, further comprising:

apply at least a portion of the primary wallet's value token to therequest; and

apply at least a portion of the sub-wallet's value token to the request.

89. The system of 83 or 88, wherein the value token of the primarywallet is applied to the request under a rule of the primary wallet orthe request.

90. The system of 85 or 88, wherein the value token of the sub-wallet isapplied to the request under a rule of the sub-wallet or the request.

91. The system of 79, wherein an aggregator system receives the request,wherein the one or more processors are further caused to:

determine at least a portion of the request may be processed in thesub-wallet; and

send the portion of the request from the aggregator system to a thirdparty.

92. The system of 76, wherein the request includes an identity of apoint of sale terminal; authentication information; an amount of apurchase; an identity of the value token issuer; an identity of avendor; an identity of a location; a time of the request; a date of therequest; information identifying a primary wallet, sub-wallet, or acombination thereof; transaction data; authentication data; orcombinations thereof.

93. The system of 76, wherein the value token comprises an electronicrepresentation of value, wherein the electronic representation of valuecomprises a credit card, debit card, gift card, prepaid telephone card,loyalty card, membership card, ticket or ticket card, entertainmentcard, sports card, prepaid card, coupon, admission pass, prepaid orpre-purchases of goods or services, cash, currency, credit card account,debit card account, merchant account, bank account, merchant-issuedcredit, merchant-issued point, merchant-issued promotional value,merchant-accepted credit, merchant-accepted point, merchant-acceptedpromotional value, or combinations thereof.

94. The system of 93, wherein the value token further comprises at leasttwo electronic representations of value of different types.

95. The system of 76, wherein the value token comprises a closed loopaccount number, wherein apply at least a portion of the value tokencomprises credit or debit a closed loop account associated with theclosed loop account number.

96. The system of 76, wherein the value token comprises an open loopaccount number, wherein apply at least a portion of the value tokencomprises credit or debit an open loop account associated with the openloop account number.

97. The system of 76, wherein apply at least a portion of the valuetoken comprises using the value token according to a set of configurablerules specifying priority of the value tokens.

98. The system of 97, wherein the priority is based on a transactioninformation variable comprising physical location of a retaileroriginating the electronic wallet request; transaction amount; type ofretailer; time of day; day of week; week of month; month of year;department of retailer originating the electronic wallet request; laneof retailer originating the electronic wallet request; identification ofchecker; parent company of a retailer originating the electronic walletrequest; value of value tokens; type of the electronic wallet request;or combinations thereof.

99. The system of 76, wherein apply at least a portion of the valuetoken comprises use the value token according to a set of configurablerules specifying percentages of the electronic wallet request to whichvalue tokens may be applied.

100. The system of 76, wherein the one or more processors are furthercaused to:

examine a rule associated with the electronic wallet.

101. The system of 100, wherein examine a rule comprises:

examine a priority of the value token.

102. The system of 100, wherein examine a rule comprises:

examine a percentage of the request;

wherein apply at least a portion of the value token comprises apply atleast a portion of the value token to the request according to thepercentage.

103. The system of 76, wherein the electronic wallet comprises a closedloop-related value token and an open loop-related value token, whereinthe one or more processors are further caused to:

select the closed loop-related value token; and

then select the open loop-related value token.

104. The system of 76, wherein the electronic wallet comprises an openloop-related value token, wherein the one or more processors are furthercaused to:

withhold the open loop-related value token from being applied to therequest.

105. The system of 76, wherein the one or more processors are furthercaused to:

exchange at least a portion of the value token of the electronic walletfor at least a portion of a second value token not located in theelectronic wallet.

106. The system of 105, wherein the one or more processors are furthercaused to:

apply an exchange rate against the second value token or an assetlocated in the electronic wallet.

107. The system of 105, wherein exchange at least a portion of the valuetoken comprises:

contact a second value token distributor; and

request the second value token distributor to provide the second valuetoken.

108. The system of 76, wherein the electronic wallet comprises a firstsub-wallet and a second sub-wallet, wherein the first sub-walletcomprises the value token, wherein the one or more processors arefurther caused to:

place the value token of the first sub-wallet into the secondsub-wallet.

109. The system of 76, wherein the one or more processors are furthercaused to:

provision the electronic wallet with the value token.

110. The system of 109, wherein the value token is provisioned in anamount different than the purchase price.

111. The system of 109, wherein provision the electronic walletcomprises encode the value token with a coupon code.

112. The system of 109, wherein provision the electronic walletcomprises add the value token to the electronic wallet.

113. The system of 76, wherein the electronic wallet comprises asavings-designated sub-wallet, wherein the one or more processors arefurther caused to:

place at least a portion of the value token in the savings-designatedsub-wallet.

114. A system comprising:

one or more processors;

a memory coupled to at least one of the one or more processors;

the memory comprising executable instructions that, when executed, causethe one or more processors to:

receive a request to process a payment transaction against an electronicwallet;

determine the request contains valid authentication information;

determine a value token, or a combination of value tokens, associatedwith the electronic wallet is capable of meeting the request; and

apply at least a portion of the value token to at least a portion of therequest.

115. The system of 114, wherein the one or more processors are furthercaused to:

accept an authentication token to access the electronic wallet.

116. The system of 115, wherein the authentication information is basedon the authentication token, wherein the authentication token comprisesa proxy card, a mobile device, a password, a biometric identifier, orcombinations thereof.

117. The system of 114, wherein the electronic wallet comprises aprimary wallet and a sub-wallet.

118. The system of 117, wherein the one or more processors are furthercaused to:

process at least a portion of the request via the primary wallet.

119. The system of 118, wherein the one or more processors are furthercaused to:

process at least another portion of the request via the sub-wallet.

120. The system of 117, wherein the primary wallet comprises the valuetoken, wherein the one or more processors are further caused to:

determine the request is related to the primary wallet;

wherein apply at least a portion of the value token comprises apply atleast a portion of the value token of the primary wallet to the request.

121. The system of 117, wherein the sub-wallet comprises the valuetoken, wherein the one or more processors are further caused to:

determine the request is related to the sub-wallet;

wherein apply at least a portion of the value token comprises apply atleast a portion of the value token of the sub-wallet to the request.

122. The system of 117, wherein the electronic wallet comprises two ormore value tokens, wherein the primary wallet comprises at least one ofthe two or more value tokens, wherein the sub-wallet comprises at leastanother of the two or more value tokens.

123. The system of 122, wherein the one or more processors are furthercaused to:

determine a portion of the request is related to the primary wallet; and

determine another portion of the request is related to the sub-wallet

124. The system of 123, further comprising:

apply at least a portion of the primary wallet's value token to therequest; and

apply at least a portion of the sub-wallet's value token to the request.

125. The system of 120 or 124, wherein the value token of the primarywallet is applied to the request under a rule of the primary wallet orthe request.

126. The system of 121 or 124, wherein the value token of the sub-walletis applied to the request under a rule of the sub-wallet or the request.

127. The system of 117, wherein an aggregator system receives therequest, wherein the one or more processors are further caused to:

determine at least a portion of the request may be processed in thesub-wallet; and

send the portion of the request from the aggregator system to a thirdparty.

128. A system comprising:

-   -   one or more processors;    -   a memory coupled to at least one of the one or more processors;    -   the memory comprising executable instructions that, when        executed, cause the one or more processors to:    -   receive a request to process a payment transaction against an        electronic wallet from a provider of a primary wallet;    -   determine a value token is capable of meeting the request; and    -   apply at least a portion of the value token to at least a        portion of the request.

129. The system of 128, wherein the one or more processors are furthercaused to:

-   -   determine the request is related to the sub-wallet;    -   wherein apply at least a portion of the value token comprises        apply at least a portion of the value token of the sub-wallet to        the request.

130. The system of 128, wherein the sub-wallet comprises asub-sub-wallet.

131. The system of 130, wherein the one or more processors are furthercaused to:

-   -   determine the request is related to the sub-sub-wallet;    -   wherein apply at least a portion of the value token comprises        apply the value token of the sub-sub-wallet to the request.

132. The system of 130, wherein the one or more processors are furthercaused to:

-   -   determine a portion of the request is related to the sub-wallet;        and    -   determine another portion of the request is related to the        sub-sub-wallet.

133. The system of 130, wherein the electronic wallet comprises two ormore value tokens, wherein the sub-wallet comprises at least one of thetwo or more value tokens, wherein the sub-sub-wallet comprises at leastanother of the two or more value tokens.

134. The system of 133, further comprising:

-   -   apply at least a portion of the sub wallet's value token to the        request; and    -   apply at least a portion of the sub-sub-wallet's value token to        the request.

135. The system of 129 or 134, wherein the value token of the sub-walletis applied to the request under a rule of the sub-wallet or the request.

136. The system of 131 or 134, wherein the value token of thesub-sub-wallet is applied to the request under a rule of thesub-sub-wallet or the request.

137. A system, comprising:

-   -   one or more processors;    -   a memory coupled to at least one of the one or more processors;    -   the memory comprising executable instructions that, when        executed, cause the one or more processors to:

receive a request related to an electronic wallet, wherein the requestcomprises an electronic wallet request, a balance inquiry request, aregistration request, an activation request, a redemption request, orcombinations thereof; and

manage the contents of the electronic wallet according to the request.

138. The system of 137, wherein manage the content comprises:

-   -   exchange at least a portion of a value token of the electronic        wallet for at least a portion of a second value token not        located in the electronic wallet.

139. The system of 138, wherein the one or more processors are furthercaused to:

-   -   apply an exchange rate against the second value token or an        asset located in the electronic wallet.

140. The system of 138, wherein exchange at least a portion of the valuetoken comprises:

contact a second value token distributor of the second value token; and

request the second value token distributor to provide the second valuetoken.

141. The system of 137, wherein the electronic wallet comprises a firstsub-wallet and a second sub-wallet, wherein the first sub-walletcomprises a value token, wherein the one or more processors are furthercaused to:

place the value token of the first sub-wallet into the secondsub-wallet.

142. The system of 137, wherein the one or more processors are furthercaused to:

-   -   provision the electronic wallet with a value token.

143. The system of 142, wherein the value token is provisioned in anamount different than the purchase price.

144. The system of 142, wherein provision the electronic walletcomprises encode the value token with a coupon code.

145. The system of 142, wherein provision the electronic walletcomprises add the value token to the electronic wallet.

146. The system of 137, wherein the electronic wallet comprises asavings-designated sub-wallet, wherein the one or more processors arefurther caused to:

place at least a portion of a value token in the savings-designatedsub-wallet.

147. A system comprising:

one or more processors;a memory coupled to at least one of the one or more processors;the memory comprising executable instructions that, when executed, causethe one or more processors to:

receive a request to process a payment transaction against an electronicwallet;

identify authentication information of the request;

identify a value token in the electronic wallet; and

apply at least a portion of the value token to at least a portion of therequest.

148. The system of 147, wherein the one or more processors are furthercaused to accept an authentication token to access the electronicwallet.

149. The system of 148, wherein the authentication information is basedon the authentication token, wherein the authentication token comprisesa proxy card, a mobile device, a password, a biometric identifier, orcombinations thereof.

150. The system of 149, wherein the electronic wallet comprises aprimary wallet and a sub-wallet.

151. The system of 150, wherein the one or more processors are furthercaused to process at least a portion of the request via the primarywallet.

152. The system of 151, wherein the one or more processors are furthercaused to process at least a portion of the request via the sub-wallet.

153. The system of 152, wherein the primary wallet comprises the valuetoken, wherein the one or more processors are further caused to:

-   -   determine the request is related to the primary wallet; and    -   determine the value token is capable of meeting the request.

154. The system of 153, wherein apply at least a portion of the valuetoken comprises apply at least a portion of the value token of theprimary wallet to the request.

155. The system of 154, wherein the sub-wallet comprises the valuetoken, wherein the one or more processors are further caused to:

-   -   determine the request is related to the sub-wallet; and    -   determine the value token is capable of meeting the request.

156. The system of 155, wherein apply at least a portion of the valuetoken comprises apply at least a portion of the value token of thesub-wallet to the request.

157. The system of 156, wherein the electronic wallet comprises two ormore value tokens, wherein the primary wallet comprises at least one ofthe two or more value tokens, wherein the sub-wallet comprises at leastanother of the two or more value tokens.

158. The system of 157, wherein the one or more processors are furthercaused to:

-   -   determine a portion of the request is related to the primary        wallet; and    -   determine another portion of the request is related to the        sub-wallet.

159. The system of 158, wherein the one or more processors are furthercaused to:

apply at least a portion of the primary wallet's value token to therequest; and

apply at least a portion of the sub-wallet's value token to the request.

160. The system of 159, wherein the value token of the primary wallet isapplied to the request under a rule of the primary wallet.

161. The system of 159, wherein the value token of the primary wallet isapplied to the request under a rule of the request.

162. The system of 159, wherein the value token of the sub-wallet isapplied to the request under a rule of the sub-wallet.

163. The system of 159, wherein the value token of the sub-wallet isapplied to the request under a rule of the request.

164. The system of 159, wherein an aggregator system receives therequest, wherein the one or more processors are further caused to:

determine at least a portion of the request may be processed in thesub-wallet; and

send the portion of the request from the aggregator system to a thirdparty.

165. The system of 164, wherein the request includes an identity of apoint of sale terminal; authentication information; an amount of apurchase; an identity of the value token issuer; an identity of avendor; an identity of a location; a time of the request; a date of therequest; information identifying a primary wallet, sub-wallet, or acombination thereof; transaction data; authentication data; orcombinations thereof.

166. The system of 165, wherein the value token comprises an electronicrepresentation of value, wherein the electronic representation of valuecomprises a credit card, debit card, gift card, prepaid telephone card,loyalty card, membership card, ticket or ticket card, entertainmentcard, sports card, prepaid card, coupon, admission pass, prepaid orpre-purchases of goods or services, cash, currency, credit card account,debit card account, merchant account, bank account, merchant-issuedcredit, merchant-issued point, merchant-issued promotional value,merchant-accepted credit, merchant-accepted point, merchant-acceptedpromotional value, or combinations thereof.

167. The system of 166, wherein the value token further comprises atleast two electronic representations of value of different types.

168. The system of 167, wherein the value token comprises a closed loopaccount number, wherein apply at least a portion of the value tokencomprises credit or debit a closed loop account associated with theclosed loop account number.

169. The system of 168, wherein the value token comprises an open loopaccount number, wherein apply at least a portion of the value tokencomprises credit or debit an open loop account associated with the openloop account number.

170. The system of 169, wherein apply at least a portion of the valuetoken comprises using the value token according to a set of configurablerules specifying priority of the value tokens.

171. The system of 170, wherein the priority is based on a transactioninformation variable comprising physical location of a retaileroriginating the electronic wallet request; transaction amount; type ofretailer; time of day; day of week; week of month; month of year;department of retailer originating the electronic wallet request; laneof retailer originating the electronic wallet request; identification ofchecker; parent company of a retailer originating the electronic walletrequest; value of value tokens; type of the electronic wallet request;or combinations thereof.

172. The system of 171, wherein apply at least a portion of the valuetoken comprises use the value token according to a set of configurablerules specifying percentages of the electronic wallet request to whichvalue tokens may be applied.

173. The system of 172, wherein the one or more processors are furthercaused to:

examine a rule associated with the electronic wallet.

174. The system of 173, wherein examine a rule comprises:

examine a priority of the value token.

175. The system of 174, wherein examine a rule comprises:

examine a percentage of the request;

wherein apply at least a portion of the value token comprises apply atleast a portion of the value token to the request according to thepercentage.

176. The system of 175, wherein the electronic wallet comprises a closedloop-related value token and an open loop-related value token, whereinthe one or more processors are further caused to:

select the closed loop-related value token; and

then select the open loop-related value token.

177. The system of 176, wherein the electronic wallet comprises an openloop-related value token, wherein the one or more processors are furthercaused to:

withhold the open loop-related value token from being applied to therequest.

178. The system of 177, wherein the one or more processors are furthercaused to:

exchange at least a portion of the value token of the electronic walletfor at least a portion of a second value token not located in theelectronic wallet.

179. The system of 178, wherein the one or more processors are furthercaused to:

apply an exchange rate against the second value token or an assetlocated in the electronic wallet.

180. The system of 179, wherein exchange at least a portion of the valuetoken comprises:

contact a second value token distributor; and

request the second value token distributor to provide the second valuetoken.

181. The system of 180, wherein the electronic wallet comprises a firstsub-wallet and a second sub-wallet, wherein the first sub-walletcomprises the value token, wherein the one or more processors arefurther caused to:

-   -   place the value token of the first sub-wallet into the second        sub-wallet.

182. The system of 181, wherein the one or more processors are furthercaused to:

provision the electronic wallet with the value token.

183. The system of 182, wherein the value token is provisioned in anamount different than the purchase price.

184. The system of 183, wherein provision the electronic walletcomprises encode the value token with a coupon code.

185. The system of 184, wherein provision the electronic walletcomprises add the value token to the electronic wallet.

186. The system of 185, wherein the electronic wallet comprises asavings-designated sub-wallet, wherein the one or more processors arefurther caused to:

place at least a portion of the value token in the savings-designatedsub-wallet.

There has been described herein an electronic value token transactionprocessing system that allows users to purchase, redeem, and/or exchangeelectronic value tokens residing in an electronic wallet. It will beapparent to those skilled in the art that modifications may be madewithout departing from the spirit and scope of the disclosure. Theembodiments described are representative only, and are not intended tobe limiting. Many variations, combinations, and modifications of theapplications disclosed herein are possible and are within the scope ofthe disclosure. Accordingly, the scope of protection is not limited bythe description set out above, but is defined by the claims whichfollow, that scope including all equivalents of the subject matter ofthe claims.

What is claimed is:
 1. A computer implemented method comprising:receiving, from a value token user, a request convert a representationof value into a value token, wherein the representation of value isassociated with a specific purchasing activity, and wherein therepresentation of value comprises an intelligent code; receiving anindication of the specific purchasing activity; converting therepresentation of value into the value token; and providing, to thevalue token user, the value token.
 2. The method of claim 1, whereinconverting the representation of value into the value token comprisesactivating the value token.
 3. The method of claim 1, wherein providing,to the value token user, the value token comprises associating the valuetoken with an electronic wallet.
 4. The method of claim 1, wherein therepresentation of value is a physical representation of value.
 5. Themethod of claim 1, wherein the representation of value is an electronicrepresentation of value.
 6. The method of claim 5, wherein therepresentation of value is displayed on a device of the value tokenuser.
 7. The method of claim 1, wherein the intelligent code comprises abarcode; a QR code; an arrangement of numerals, letters, symbols,images, and/or colors; an electromagnetic signal (e.g., near fieldcommunication (“NFC”), infrared, RFID); a mechanical wave (e.g., sound);or combinations thereof.
 8. The method of claim 1, wherein theintelligent code is unique to the value token.
 9. The method of claim 1,wherein the value token comprises points, miles, dollars, Google® cashor credits, Pay Pal® currency, or Facebook® electronic currency.
 10. Themethod of claim 1, wherein the representation of value comprises aloyalty card, a membership card, a ticket, an entertainment card, asports card, a prepaid card, a coupon, an admission pass, orcombinations thereof.
 11. The method of claim 1, wherein providing, tothe value token user, the value token is subsequent to the specificpurchasing activity.
 12. A system comprising computer devices configuredto: receive, from a value token user, a request convert a representationof value into a value token, wherein the representation of value isassociated with a specific purchasing activity, and wherein therepresentation of value comprises an intelligent code; receive anindication of the specific purchasing activity; convert therepresentation of value into the value token; and provide, to the valuetoken user, the value token.
 13. The system of claim 12, wherein thevalue token is activated to convert the representation of value into thevalue token.
 14. The system of claim 12, wherein provide, to the valuetoken user, the value token comprises associating the value token withan electronic wallet.
 15. The system of claim 12, wherein therepresentation of value is a physical representation of value.
 16. Thesystem of claim 12, wherein the representation of value is an electronicrepresentation of value.
 17. The system of claim 16, wherein therepresentation of value is displayed on a device of the value tokenuser.
 18. The system of claim 12, wherein the intelligent code comprisesa barcode; a QR code; an arrangement of numerals, letters, symbols,images, and/or colors; an electromagnetic signal (e.g., near fieldcommunication (“NFC”), infrared, RFID); a mechanical wave (e.g., sound);or combinations thereof.
 19. The system of claim 12, wherein theintelligent code is unique to the value token.
 20. The system of claim12, wherein the value token comprises points, miles, dollars, Google®cash or credits, Pay Pal® currency, or Facebook® electronic currency.21. The system of claim 12, wherein the representation of valuecomprises a loyalty card, a membership card, a ticket, an entertainmentcard, a sports card, a prepaid card, a coupon, an admission pass, orcombinations thereof.
 22. The system of claim 12, wherein provide, tothe value token user, the value token is subsequent to the specificpurchasing activity.